Skip to main content

Organization, team & roles

Organization settings​

Under Settings:

  • Profile shows your name. Your email and role are shown but changed elsewhere.
  • Organization holds your organization's name. The slug is used for API identification and cannot be changed. Only admins and owners can edit organization settings.
  • Security covers password, two-factor, and active sessions.

The Danger Zone on the Organization tab lets an owner delete the whole organization. This is irreversible.

Roles & permissions​

Every feature in the portal is gated by permissions, and permissions are grouped into roles. Manage them under Admin → Roles.

There are built-in system roles (owner, admin, manager, organization_manager, member), and you can create custom roles with a display name, description, and a specific set of permission checkboxes (grouped by category, for example orders.write, bridges.sync, carrier_accounts.delete).

Because the UI respects these permissions, what a teammate can see and do follows from their role. Only someone with bridges.write sees Add Bridge, and only admins see Create API Key.

Fulfillment Operations roles​

Owners and administrators receive Fulfillment Operations access by default. Custom roles can separate viewing, setup, approval, and policy management with:

  • fulfillment_operations.read
  • fulfillment_operations.write
  • fulfillment_operations.approve
  • fulfillment_operations.policy_manage
  • fulfillment_operations.emergency_manage

Giving someone approval access does not automatically give them policy-management access. Elevated action plans still require an organization owner.

Next steps​