SAM Users & Roles

SAM (Soracom Access Management) lets you create sub-accounts with granular permissions under your operator account. Define roles with specific API and console access levels, then assign them to team members — so each person only has access to the resources and actions they need.

What it does

• Sub-accounts: Create individual user accounts under a single operator for team collaboration
• Role-based access control: Define roles with fine-grained permissions for API operations and console features
• Permission policies: Write JSON policies that allow or deny specific actions on specific resources
• API key management: Generate API keys scoped to individual SAM users for programmatic access
• Separation of duties: Restrict billing access, SIM management, or configuration changes to authorized users

Common use cases

• Giving developers read-only access to production SIM data
• Restricting billing and payment management to finance team members
• Creating a CI/CD service account with only the permissions needed for deployments

Related

• Operators — Root account that owns SAM users
• MFA & Security — Enforce multi-factor authentication on SAM users
• Audit Logs — Track actions performed by each SAM user