AvailableImplemented

Makerbay Platform

The control layer behind every enabled module.

Makerbay starts with one organisation context for members, roles, permission keys, enabled products, and audit activity. Every bundle uses that same foundation.

In the application

Set access once, then let teams work in context.

The shared application foundation manages organisation context, members, custom roles, permission keys, role assignments, and audit activity.

Role and permission changes are applied through the Platform; affected users may need to refresh or sign in again to receive the updated session context.

Organisation workspace and member context
Role catalogue and custom-role creation
Permission keys grouped by module
User-to-role assignment
Administrator activity and data-change logs

Access workflow

  1. Step 1

    Create or select the organisation workspace.

  2. Step 2

    Create a role and choose the permission keys it needs.

  3. Step 3

    Assign members to the role and refresh their session when access changes.

  4. Step 4

    Review important administrative activity in Audit Logs.

Roles have purpose

Create roles around responsibility, select permission keys, and assign the people who need them.

Permission keys stay clear

Permissions are grouped by module so administrators can understand the access they are granting.

Modules inherit the foundation

Enable a bundle without starting another user directory or rebuilding access from scratch.