> ## Documentation Index > Fetch the complete documentation index at: https://docs.satyakod.com/llms.txt > Use this file to discover all available pages before exploring further. # Team and roles > Invite people to your workspace, choose what each role can do, and work across several workspaces. ## Invite people ![Settings → Team & roles: members, their roles and two-step verification](https://docs.satyakod.com/images/screenshot-placeholder.svg) Settings → Team & roles: members, their roles and two-step verification Admins invite people in **Settings → Team & roles → Invite member**: paste one or more work emails (separated by commas or new lines), choose a role and **Send invites**. Each person gets an email; the invite expires after 7 days. People already in the workspace are skipped. When your workspace [requires SSO](https://docs.satyakod.com/guides/security-and-sso.md#single-sign-on), they join through your identity provider; otherwise new people set a password and people who already have an account sign in. From a member's **⋯** menu, admins can **Resend invite** (the old link stops working), **Cancel invite** or **Remove from workspace**. Removing someone ends their access at once; what they did stays in the audit log. Admins can't change their own role or remove themselves, and a workspace always keeps at least one admin. If your company provisions people with SCIM, they join as viewers from your identity provider; see [Security and SSO](https://docs.satyakod.com/guides/security-and-sso.md). ## Roles Choose each person's role from the member list. | Role | For | Can | | - | - | - | | **Owner** | The person who set the workspace up (one per workspace) | Everything an Admin can, plus the business's billing details; hands ownership on in **Settings → Team & roles → Ownership** | | **Admin** | Brand owners and IT | Everything, including team, security, integrations and billing, except the billing details | | **Brand protection** | Investigators | Batches, revocation, alerts and their rules, design edits, loyalty | | **Packaging engineer** | Packaging and print | Products, Code Studio designs and approval | | **Supply chain** | Plant and logistics | Products, batches, print line printers, alerts | | **Billing** | Finance | Invoices, payments and the subscription; loyalty payouts | | **Viewer** | Everyone else | See scans, batches, alerts and reports | | **Field scanner** | Your own staff in the field (audits, goods-in checks) | Scan in the Satyakod app; no dashboard pages | ### Field scanners Field scanners sign in to the Satyakod app on their phone with their work email and scan there; the dashboard sends them to the app. Each field scanner, and each pending invitation for one, uses a **field scanner seat**: your plan includes some, and seat packs add more (Billing). The member list shows how many are in use; removing a field scanner or cancelling their invitation frees the seat at once. Admins can also invite field scanners from the app (**Account → Invite field scanners**). A field scanner's scans are recorded as theirs: **Scans** shows the channel *Field scanner* with their name (select it for all their scans), along with where they were when they scanned. A field scanner is signed in on one phone at a time: signing in on another signs the first out. If one person's account scans in places too far apart for the time between them, the **Scanner account shared** alert opens. #### Field audits and goods-in In the app, a field scanner starts a check from **Account → Field checks**: * **Field audit**: the stock on a shop's or warehouse's shelf. They say where they are, then scan. * **Goods-in**: a delivery as it arrives. They say who it's from and, optionally, the invoice or GRN number, the batch on the paperwork and how many packs it should have. Every scan while the check is open counts in it; the check shows the packs scanned (a pack scanned twice counts once), how many were genuine, suspicious or counterfeit, and for goods-in how many came from other batches and how many genuine packs are short. Starting a new check finishes the open one. In the dashboard, **Scans → Field checks** lists everyone's checks; open one for what it found and **See its scans**. Counterfeit scans in a check raise alerts like any other scan. In detail (the **Roles** table under the member list shows the main rows): | Action | Admin | Brand protection | Packaging engineer | Supply chain | Billing | Viewer | | - | - | - | - | - | - | - | | See scans, batches, alerts | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | | Add and edit products | ✓ | | ✓ | ✓ | | | | Create and sign batches | ✓ | ✓ | | ✓ | | | | Revoke codes | ✓ | ✓ | | | | | | Work alerts | ✓ | ✓ | | ✓ | | | | Edit alert rules and distributors | ✓ | ✓ | | | | | | Edit Code Studio designs | ✓ | ✓ | ✓ | | | | | Approve designs for production | ✓ | | ✓ | | | | | Loyalty: view / payouts / settings | ✓ / ✓ / ✓ | ✓ / – / – | | | ✓ / ✓ / – | | | Billing: pay and change the plan | ✓ | | | | ✓ | | | Set a print line's Zebra printer | ✓ | | | ✓ | | | | Team, security, API keys, integrations, print lines, branding, scan page | ✓ | | | | | | | Export the audit log; download offline verification keys | ✓ | | | | | | ## Custom roles When no built-in role fits, Admins build one in **Settings → Team & roles → Custom roles**: give it a name and tick what it can do (create batches, revoke codes, approve designs, manage billing and so on). It then appears in the role list when you invite someone or change their role, and as a column in the roles table. A role people still have can't be deleted; give them another role first. ## Several workspaces Each workspace has its own codes, keys, team and billing, for example one per company or country. Switch between yours from the workspace name in the top bar. **Settings → Workspaces** lists them: **Make default** chooses the one that opens after you sign in, and **Leave** takes you out of one (not your only one, not if you're its only admin, and not when your identity provider manages it). **Request a new workspace** (from the switcher) sends Satyakod a name and notes; we set it up and make you its admin. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.