Product docs
Enterprise organizations
One deployment can serve more than one customer. An organization is that customer's team. A person belongs to one organization.
License and seats
A platform admin creates the organization, chooses the license, and sets the seat limit. A new organization starts without an enterprise license, with 25 seats. The license is none or enterprise. Stripe checkout is not part of this path.
An enterprise license grants Pro tools to members in the order they joined, up to the seat limit. Organization admins count as seats. A personal Pro plan still applies when the organization license is none. Lowering the seat limit leaves the members in place. Coverage follows the earliest seats.
Members
An organization admin adds members and invites by email. An existing account joins when a seat is open. Any other email waits until that person signs in. A full seat leaves the invite in place. Appointing an organization admin is a platform admin action.
Address
When the root domain is set, the organization address is the slug under that root, on the /IandE path. The host selects the organization. Membership is what unlocks tools. A signed-in person who is outside the organization does not see its roster.
Brand and procedures
Members see that organization's logo, header, and colors. An organization admin can save that brand for their own organization.
A procedure share stays inside one organization, or between people who are outside every organization. A share across organizations is refused. Sharing stays explicit: an organization admin does not receive every procedure in the organization.