How Makerbay works
A clear path from organisation setup to useful work.
Makerbay does not ask every team to start with a new identity, role model, or access process. Establish the foundation once, then enable the modules that make sense.
- 01
Start with the organisation
Create or select the Makerbay organisation workspace that becomes the common context for every person and module.
- Organisation context keeps users, teams, and product work connected.
- Members enter the shared workspace before working in any enabled module.
- 02
Set roles and permissions
Administrators define the responsibilities people have, then assign the users who need that access.
- Create a role and select permission keys by module.
- Assign the role to organisation members and refresh sessions when access changes.
- 03
Enable the workspaces
Choose the product modules that support the work you need to run now—HR, customer work, delivery, staffing, or another focused area.
- Available, partial, and planned experiences are shown honestly in the catalogue.
- Every enabled module uses the same organisation and access foundation.
- 04
Run work and review activity
Teams work in the right module while the Platform keeps role context and important activity connected.
- Use application-specific workflows such as issue movement, lead follow-up, staffing assignment, or people operations.
- Administrators use audit activity to follow significant access and data changes.
Next step
Choose the first module for your rollout.
The product guide shows current capabilities, partial implementation, and planned direction for every module.