Admins
Admins have full access. They can:- Configure workspace settings, branding, and custom domains
- Invite team members and assign roles
- Install, configure, and remove apps
- Build new apps with the app builder
- Manage billing
- Adjust visibility and permissions on every app
Staff
Staff have operational access. They can:- Service clients through whatever apps you’ve made available to them
- View and update client records
- Run day-to-day work
- Change workspace-level settings
- Install or build apps
- Invite other internal users
The app builder is admin-only during the beta. Staff can use the apps you build, but they can’t build their own. This is likely to remain true at GA, but if it changes the docs will reflect it.
Inviting your team
From the Dashboard, open Settings and find the team management section. Add a team member by email, set their role, and send the invite.Internal user roles
In the Assembly Studio guide
How your apps treat roles
When you describe an app to the app builder, the planning step asks how admins and staff should differ inside that app — if at all. Common patterns:Same experience for both
Same experience for both
Most apps. Admins and staff both use the app the same way. The app builder defaults here unless you say otherwise.
Admins configure, staff execute
Admins configure, staff execute
Admin sees configuration screens (defining categories, setting thresholds, managing templates). Staff sees only the working interface.
Staff cannot delete or approve
Staff cannot delete or approve
Admins are the gate for destructive or high-stakes actions. Staff can do everything else.
Admins see metrics, staff see queues
Admins see metrics, staff see queues
Admins get the rollup view (totals, trends, team performance). Staff get the actionable list of what to do next.