Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.bfl.ml/llms.txt

Use this file to discover all available pages before exploring further.

Collaborate with your team by inviting members to your organizations and projects. Our role-based access control lets you give each team member exactly the permissions they need.

​
Roles Overview

When you invite someone to an organization, they get access based on their role:
Full control over the organization — manage members, billing, settings, and all projects.
Build and ship — create projects, manage API keys, and view usage.
Handle finances — manage credits and subscriptions, view usage (no API access).
Read-only access — view everything, change nothing.
Playground users — read-only access across the organization, plus the ability to generate images in the Playground. Intended for team members who should be able to create in the Playground without any configuration or billing access.
Organization roles are automatically inherited by every project within the organization.

​
Inviting Team Members

Inviting someone to your organization gives them access based on their role:
1

Navigate to Members

In your organization sidebar, click Members
2

Click Invite Member

Click the Invite Member button
3

Enter details

Enter their email address and select their role
4

Send invitation

Click Send Invitation — they’ll receive an email with a link to join
Invitations expire after 7 days. You can cancel pending invitations and resend if needed.

​
Managing Members

Change Role

Go to Members, click a member’s current role, and select a new one. Changes take effect immediately.

Remove Member

Go to Members, find the member, and click remove. They immediately lose access.

Cancel Invitation

Go to Members, find the pending invitation, and click Cancel to revoke it.
When you remove someone, their API keys remain active. Rotate keys if the removed member had access to them.

​
Best Practices

  • Make 2-3 people Administrators for redundancy
  • Use Developer role for engineers
  • Consider Billing Manager for finance/ops
  • Create separate organizations per client, OR
  • Use project-only access for client stakeholders
  • Keep API key access limited to your team
  • Use Administrators sparingly (principle of least privilege)
  • Billing Manager for finance team
  • Viewer role for stakeholders who need visibility
  • Project-only access for contractors

​
Activity Tracking

All member-related actions are logged in your organization’s Activity Log: invitations sent, invitations accepted, role changes, and member removals. This provides a complete audit trail for compliance and security reviews.

​
Next Steps

Organizations & Projects

Learn more about structuring your workspace

Credits & Billing

Manage your credits and billing