> ## Documentation Index
> Fetch the complete documentation index at: https://studio.assembly.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Internal users

Internal users are the people on your side of Assembly Studio. They sign into theDashboard, manage clients, run apps, and (with the right role) build new apps. There are two roles.

## 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

Most workspaces have one or two admins. Anyone who needs to change platform-level settings is an admin.

## 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

They cannot:

* Change workspace-level settings
* Install or build apps
* Invite other internal users

Staff is the right role for team members who execute on client work but don't manage the platform itself.

<Note>
  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.
</Note>

## 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.

<Card title="Internal user roles" icon="users-gear" href="https://assembly.com/guide/internal-user-roles">
  In the Assembly Studio guide
</Card>

## 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:

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  <Accordion title="Admins configure, staff execute">
    Admin sees configuration screens (defining categories, setting thresholds, managing templates). Staff sees only the working interface.
  </Accordion>

  <Accordion title="Staff cannot delete or approve">
    Admins are the gate for destructive or high-stakes actions. Staff can do everything else.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>

You don't have to think about these patterns up front. The app builder will surface the question if it matters for your app.

placeholder