Organization Management: Teams, Billing, and API Keys

Sire is built for collaboration. Our Organization Management tools help you scale automation across your entire company while maintaining control over security, costs, and access.

Team Management

A Sire organization (a "Tenant") can have multiple users. Administrators can manage the team from Settings > Team.

1. Invite Members: Click Invite Member and enter their work email.
2. Define Roles: Assign a role to each member:
   • Owner: Can manage billing and all settings.
   • Editor: Can create and run workflows.
   • Viewer: Read-only access.
3. Remove Access: At any time, an Owner can revoke a member's access, instantly removing them from the tenant.

RBAC Permission Matrix

The table below shows what each role can do across the platform.

Role Assignment Rules

• Every organization must have at least one Owner.
• Only Owners can promote members to Owner or demote other Owners.
• Editors cannot escalate their own permissions.
• API keys inherit the permissions of the user who created them.

Billing and Subscriptions

Sire offers tiered pricing plans to match your organization's needs. You can manage your subscription from Settings > Billing.

• Free Tier: Great for getting started. Includes a base number of monthly executions and standard MCP support.
• Pro Tier: For growing teams. Adds unlimited executions, priority support, and higher token budgets for AI generation.
• Business/Enterprise Tier: For mission-critical scale. Includes multi-region support, SSO (Okta/GitHub), and customized security controls.

Usage Tracking

The Usage Dashboard provides a real-time view of your consumption:

• Execution Count: Number of workflow runs this month.
• Token Usage: AI generation tokens consumed.
• Storage: Total size of artifacts and semantic memory.

API Keys and Service Accounts

For programmatic access to Sire (e.g., triggering a workflow from a CI/CD pipeline or a custom application), you can create API Keys.

1. Navigate to Settings > API Keys.
2. Click Create API Key.
3. Copy the Key: The key is shown only once. Store it securely in your own secret manager.
4. Manage Permissions: API keys inherit the permissions of the user who created them (Owner or Editor).

Scoped Tokens

For advanced security, you can create scoped tokens that are limited to specific workflows or read-only actions.

Single Sign-On (SSO)

Enterprise customers can simplify user management by connecting their identity provider.

• GitHub OAuth: Allow your team to sign in with their GitHub identities.
• Google OAuth: Connect your Google Workspace.
• Okta/SAML: Enterprise-grade identity federation.

Organization Settings

• Tenant Name: Update the name of your organization.
• Default Region: Choose where your workflows should be executed by default (e.g., us-east-1, eu-west-1) to minimize latency and meet data residency requirements.
• Artifact Retention: Set how long files generated by workflows are kept before being automatically deleted.

Administrative Audit Log

For organizations with high security requirements, the Admin Audit Log tracks every administrative action taken within the tenant.

• Who invited a new user?
• When was the billing plan updated?
• Who revoked an API key?
• Which admin changed a security setting?