Organizations
Understand how organizations, sub-accounts, roles, and account switching work in ModelBoard for Business, Studio, and Enterprise teams.
What an organization is in ModelBoard
An organization in ModelBoard represents a business, studio, or enterprise entity that coordinates work across multiple people and profiles in the adult entertainment industry.
An organization has its own profile, settings, and features, and then links team members to that profile as sub-accounts with specific roles and permissions.
ModelBoard is the operating system and professional networking platform for the adult entertainment industry. Organizations sit at the center of that experience for teams and companies.
Organizations at a glance
Organization profile
A top-level business, studio, or enterprise profile that owns settings, billing, and organization-wide features.
Sub-accounts & roles
Team members connect as sub-accounts with a role of owner or staff. Permissions are role-based, not free-form.
Account switching
A single user can switch between creator, business, studio, and enterprise contexts through the account switcher.
Organization profiles vs sub-accounts
Organization structures in ModelBoard are built from two pieces: a primary organization profile and linked sub-accounts for each team member.
Organization profiles
Organization profiles represent the business entity itself:
- A Business, Studio, or Enterprise profile
- Owns the brand identity, settings, and organization-level features
- Acts as the "parent" that other profiles connect to
The organization profile is what you see when you operate as the company: configuring studio pages, managing talent, handling licensing apps, and so on.
Sub-accounts (team member accounts)
Sub-accounts represent people who work within an organization:
- Created as separate profiles linked to the organization
- Have a role of owner or staff
- Log in as themselves but act on behalf of the organization when switched into that context
This design keeps each person's identity and access separate, while still letting them act inside one or more organizations.
Use separate sub-accounts for each person in your team. Do not share logins. This keeps permissions clear and makes audits accurate.
Roles in an organization: Owner vs Staff
ModelBoard has two organization-level roles: Owner and Staff. There is no separate admin role.
Use this section to decide who should hold which role in your organization.
Owners control the organization identity and team access. Each organization has at least one owner.
Common responsibilities for owners:
- Create and configure the organization profile
- Approve or reject join requests from new sub-accounts
- Manage staff access and role changes
- Handle sensitive settings and ownership transfers
Owners are the only role that can approve membership and confirm transfers between organizations.
Assign owner only to people you fully trust with your organization's identity, relationships, and sensitive configuration.
Staff accounts are team members who work inside the organization without full ownership control.
Typical staff responsibilities include:
- Operating day-to-day workflows (for example, managing shoots, collabs, or portfolios on behalf of the org)
- Handling communication and coordination in the organization's context
- Using apps and features assigned to the organization
Staff permissions can be more granular depending on whether the organization is a Business, Studio, or Enterprise account, but staff never gains full ownership or approval rights.
How organization membership works
Membership in an organization is always request-based and must be approved. ModelBoard does not use open invite links or auto-join flows.
Join and invite flow overview
1. Create or identify the organization
If you are setting up the team, start by creating or claiming the Business, Studio, or Enterprise organization profile that represents your company.
If your organization profile already exists, confirm who the current Owner is. They will handle approvals.
2. Submit a join request as a sub-account
When someone wants to join the organization, they submit a join request as a sub-account linked to that organization.
This creates a pending membership request that signals the owner to review the new team member.
3. Owner approves or rejects the request
Organization owners review pending join requests and choose to approve or reject.
- Approve: the sub-account becomes a member of the organization with the assigned role (owner or staff).
- Reject: the pending request is closed and access is not granted.
4. Membership becomes active
After approval, the new member sees the organization in their account switcher and can operate in that context according to their role.
The request-based flow ensures your organization stays secure and intentional about who has access.
All membership changes flow through explicit join requests and approvals. There are no public invite links that allow unknown users to join your organization.
Transfers between organizations
Sometimes a profile needs to move from one organization to another (for example, when a studio changes management or an agency restructures).
Transfers follow an approval-based flow similar to membership:
- A transfer request is created to move ownership or link a profile to a different organization.
- Relevant owners review and approve or decline the transfer.
- Approved transfers are recorded for auditability and future reference.
Transfers help you keep historical continuity while still reflecting changes in how your business is structured.
Ownership and role changes are audited behind the scenes, so you retain a trail of who controlled an organization and when.
Switching between accounts and organizations
Many people on ModelBoard wear multiple hats: creator, studio staff, business owner, or enterprise manager. The account switcher lets you move between these roles without multiple logins.
When you see the account switcher
You see the account switcher when your user has access to more than one profile, for example:
- Your personal creator or professional profile
- One or more Business or Studio organizations as owner or staff
- One or more Enterprise organizations, possibly linked to multiple studios
How to switch between accounts
1. Open the account switcher
From the main navigation, open the account switcher. You will see a list of profiles and organizations your user can act as.
Each entry represents a distinct context (for example, "Jane as Creator", "Sunset Studios", "Aurora Talent Agency").
2. Choose the profile or organization
Select the profile or organization you want to switch into.
ModelBoard updates your active context to that selection. Navigation, features, and data now reflect that account.
3. Confirm you are in the right context
Check the header or context indicator to confirm you are acting as the intended profile or organization.
Before performing sensitive actions (like approvals or configuration changes), always verify you are in the correct organization.
Treat the account switcher as the "hat" you are wearing. Make sure you are wearing the right hat before approving requests or changing settings.
Enterprise organizations and studio links
Enterprise organizations often manage multiple studios, brands, or subsidiaries. To support this, ModelBoard lets Enterprise accounts link directly to Studio organizations.
Conceptually, this works as:
- An Enterprise profile sits above one or more Studio profiles.
- Enterprise owners can switch into linked studios through the same account switcher flow.
- Linked studios retain their own identity while still rolling up to the enterprise for coordination and oversight.
This structure is useful for:
- Agencies managing multiple production studios
- Holding companies coordinating several brands
- Platforms with separate but related studio entities
Under the hood (for technical readers)
If you work with integrations or need to design processes around ModelBoard's structure, it helps to understand how organizations are modeled internally.
This section describes concepts at a high level and is not an API reference. For concrete endpoints and schemas, refer to the API Reference.
- Organization profiles are special profiles whose type is business, studio, or enterprise.
- Team members are sub-accounts linked via an internal organization identifier.
- Roles are captured as owner or staff at the sub-account level; there is no third admin role.
- Membership changes (joins, approvals, rejections, transfers) are handled through dedicated request objects and backend workflows.
- Enterprise-to-studio relationships are modeled as links that allow switching from the enterprise context into a specific studio context.
This model keeps every action tied to a specific profile and role, which supports clear auditing and reliable permission checks.
Security and access control
Security for organizations is based on roles and approvals, not shared credentials or open links.
Key principles:
- Each person uses their own login and becomes a sub-account of the organization.
- Owners must approve new members and ownership or organization transfers.
- There are no public invite URLs that allow unknown users to join.
- Sensitive actions and ownership changes are recorded for auditability.
Never share your personal login with team members. Instead, add them as staff or owners through the join-and-approve flow so their actions are tracked correctly.
Next steps
Use these resources to go deeper into how organizations fit into the rest of ModelBoard.
Account Types
See how Business, Studio, Enterprise, and individual profiles relate to each other.
Features
Understand which features become available when you operate as an organization.
Quickstart
Set up your first profile, then attach or create an organization and start collaborating.
Help Center
Browse guides and troubleshooting articles, or reach out if you are stuck on an organization flow.
Last updated 2 weeks ago
Built with Documentation.AI