Skip to content

Roles & Permissions

Wire uses role-based access control (RBAC) to manage permissions within organizations. Each member has a role that determines what actions they can perform.

RoleDescription
OwnerFull control over the organization
AdminManage members, containers, and billing
MemberFull container management, read-only org settings

The owner has complete control over the organization.

Permissions:

  • Create, read, update, and delete the organization
  • Manage all members (invite, remove, change roles)
  • Access billing and subscription settings
  • Full container management including admin operations
  • Container Management page: view all org containers, pause, delete, manage sharing
  • Configure organization-wide settings

Notes:

  • The user who creates an organization is automatically the owner
  • Organizations can have multiple owners
  • There must always be at least one owner

Admins can manage team members and containers but cannot modify organization-level settings.

Permissions:

  • View organization details
  • Invite new members
  • Remove members (except owners)
  • Change member roles (except to/from owner)
  • Full container management including admin operations
  • Container Management page: view all org containers, pause, delete, manage sharing
  • Access billing settings

Cannot:

  • Update organization name or settings
  • Delete the organization
  • Remove or demote owners

Members can create and manage their own containers, upload files, and trigger analysis. They can only access containers they created or were explicitly shared with.

Permissions:

  • View organization details and member list
  • Create containers
  • Upload and delete files in containers they have editor or admin access to
  • Update container name and description
  • Trigger analysis
  • Trash and restore containers
  • Invite new members
  • Use MCP tools on accessible containers
  • View billing balance (read-only)

Cannot:

  • See containers created by others (unless shared)
  • Upload files to containers without an explicit editor or admin grant
  • Pause or unpause containers
  • Change container visibility
  • Change analysis cadence
  • Permanently delete containers
  • Migrate containers to another organization
  • Access the Container Management page
  • Change member roles
  • Modify organization settings
  • Purchase credits or configure billing

These permissions apply at the organization level, regardless of container grants:

ActionOwnerAdminMember
Create containers
Container Management page
Pause / unpause
Change visibility
Change analysis cadence
Permanently delete
Migrate to another org

Containers have two visibility settings:

  • Private - Only the creator and people with explicit grants can access
  • Public - Anyone with the MCP URL can read (no authentication required)

Containers use a separate permission layer from organization roles. When you share a container with someone, you assign a container-level permission:

Container PermissionAccess
ViewerView, search, explore
EditorViewer permissions, plus write, delete, upload files, analyze
AdminFull access including settings and sharing

The container creator automatically gets admin permission. Organization owners and admins can see all containers for billing and usage purposes, but need an explicit grant to edit containers they didn’t create.

See Sharing Containers for a step-by-step guide.

  1. Go to Organization Settings
  2. Click Members
  3. Click Invite Member
  4. Enter email and select role
  5. Click Send Invitation

The invited user will receive an email with a link to join your organization.

  1. Go to Organization SettingsMembers
  2. Find the member
  3. Click on their current role
  4. Select the new role
  1. Go to Organization SettingsMembers
  2. Find the member
  3. Click Remove
  4. Confirm removal

Removing a member immediately revokes their access to all containers in the organization.