We are using self-hosted OpenPanel and noticed that a user with the org:member role can select New organization, create a separate organization, become its administrator, invite users, and create projects. Is this intentional?
We understand that org:member limits permissions only within the current organization, while creating a new organization is treated as an account-level action. However, in a controlled self-hosted environment, this allows regular customer users to create unmanaged organizations, projects, invitations, and unnecessary database records.
Could OpenPanel add a configuration option or platform-level permission that allows organization creation to be restricted to designated administrators?
Ideally:
- Platform administrators can create organizations.
- Regular members cannot create organizations.
- New organization is hidden when the user lacks permission.
- The organization-creation endpoint enforces the same restriction server-side.
This would be particularly helpful for self-hosted deployments where registration and organization provisioning are centrally managed.
We are using self-hosted OpenPanel and noticed that a user with the org:member role can select New organization, create a separate organization, become its administrator, invite users, and create projects. Is this intentional?
We understand that org:member limits permissions only within the current organization, while creating a new organization is treated as an account-level action. However, in a controlled self-hosted environment, this allows regular customer users to create unmanaged organizations, projects, invitations, and unnecessary database records.
Could OpenPanel add a configuration option or platform-level permission that allows organization creation to be restricted to designated administrators?
Ideally:
This would be particularly helpful for self-hosted deployments where registration and organization provisioning are centrally managed.