​

Create an organization

Create an organization when Starfire resources should belong to a team rather than one person’s account.

​

Before creating

Decide:

• who should own the organization
• whether the organization needs shared billing
• which members need initial administrative access
• whether production developer resources should be organization-owned
• which existing personal projects may eventually need transfer

​

Create the organization

1. Open the Organizations area.
2. Create a new organization.
3. Choose a clear organization name.
4. Confirm the initial owner.
5. Configure billing or plan context when required.
6. Invite only the first administrators/members you actually need.
7. Review organization policy before moving production work into it.

​

Ownership

The owner role is the strongest organization-level authority. It should be assigned deliberately because ownership can include billing, policy, membership, and destructive organization actions.

​

After creation

Set up:

• membership and roles
• seats/billing
• projects
• Knowledge
• model/feature policies
• developer applications/service accounts

​

Personal resources do not automatically move

Creating an organization does not automatically convert a person’s projects, API keys, subscriptions, or Knowledge into organization-owned resources. Review each important resource and move/transfer it only through supported product flows.