+Penpot Enterprise gives organizations the tools to govern how design work happens across their teams: from creating a structured org and managing members, to applying fine-grained permissions and configuration through the Admin Console.
+ +Penpot Enterprise is the plan that unlocks organizational governance features. While Penpot remains free and unlimited as an open-source platform, Enterprise adds a layer of control on top: the ability to create Organizations, manage teams under it, and apply configuration settings that define what members can and cannot do.
+The key concepts you'll work with:
+To create an organization, you first need to upgrade to the Enterprise plan. Click "Create Organization" to begin. Once the subscription process is complete, you'll be redirected to the Admin Console to finish creating your organization.
+ +Creating an organization is as easy as giving it a name.
+Once the organization is created, you'll be taken to the Admin Console. At this point, the organization has one member: you, the owner.
+ +The Admin Console is the admin interface for your organization. Only the organization owner can access it.
+The Admin Console includes:
+ +
+An organization groups one or more Teams under a shared governance structure. Teams continue to work just as they do in standard Penpot, with the added layer that the org owner can apply configuration that affects all members across the organization's teams.
+Teams inside an organization inherit the governance settings applied at the org level via the Admin Console. The structure is:
+ +
+Team members work within projects and files as usual. What changes under Enterprise is the org owner's ability to restrict or govern that work from the Admin Console.
+Within each team, the standard Penpot roles apply.
+ +At launch, an organization has a single member: the owner. Additional members are brought in by being part of a team added to the organization, being invited to teams within the organization, or being directly invited to the organization by the owner.
+The Admin Console provides a unified view of all members across teams within the organization.
+ +
+Modules are the configurable governance capabilities available to Enterprise organizations. Each Module is made up of one or more Controls: the individual settings that define who can do what, and where.
+Modules are configured from the Admin Console and apply organization-wide.
+ +| Modules | +What it does | +
|---|---|
| Single Sign-On (SSO) | +Requires all org members to authenticate through a private auth system. Refines Penpot's existing SSO support. | +
| Advanced permissions | +Defines who can create, view, edit, administer, or share teams, projects, and files. Also controls who can invite new members to teams. | +
Advanced Permissions gives the organization owner fine-grained control over what members can do across all teams in the organization. Rather than relying on the default Penpot team roles alone, this module lets you restrict or open up specific actions at the organization level.
+ +The Advanced Permissions module is made up of individual Controls. Each Control governs a specific action, and each has a set of options to choose from. The selected option becomes the rule for the entire organization.
+ +Advanced Permissions is configured from the Admin Console. Changes apply to all teams within the organization immediately.
+Advanced Permissions works on top of the standard Penpot team roles (Viewer, Editor, Admin, Owner). It does not replace them. Think of it as a ceiling: even if a member's team role would normally allow an action, an Advanced Permissions Control can prevent it organization-wide.
+For example, if “New team members” is set to "Organization members only," a team owner who would normally be able to invite anyone will find that option restricted to people who are already part of the organization.
+ +When an organization is first created, all controls are configured with the most permissive setting; the same setting is used by all teams that are not part of any organization. No behavior changes until you actively configure a Control.
+ +Yes. You can create more than one organization under a single Enterprise subscription. Each has its own Admin Console.
+ +Your organization and its teams remain accessible, but governance features (Modules and Controls) will no longer be enforced.
+ +No. A team belongs to a single organization.
+ +No. Access to the Admin Console is currently exclusive to the organization owner. If another user attempts to access the Admin Console URL, they will see a 404 page.
+ +It's the human-readable name used to identify your organization in the UI, in emails, and in URLs. It is not your official billing name. You can change it at any time without affecting navigation or functionality.
+ + + + diff --git a/docs/user-guide/account-teams/index.njk b/docs/user-guide/account-teams/index.njk index e03ed12133..6c7db02e4c 100644 --- a/docs/user-guide/account-teams/index.njk +++ b/docs/user-guide/account-teams/index.njk @@ -13,7 +13,13 @@ desc: Begin with the Penpot user guide! Get quickstarts, shortcuts, and tutorialAccess your account settings and manage personal access tokens
-Learn how the Enterprise plan works and what it includes
+ +Create and manage your teams
diff --git a/docs/user-guide/account-teams/projects-files.njk b/docs/user-guide/account-teams/projects-files.njk index 9345cd4f45..393dddb635 100644 --- a/docs/user-guide/account-teams/projects-files.njk +++ b/docs/user-guide/account-teams/projects-files.njk @@ -1,6 +1,6 @@ --- title: Projects and Files -order: 3 +order: 4 desc: Learn how to organize your work in Penpot. Create, manage and organize projects and files, work with drafts, and handle deleted items. --- diff --git a/docs/user-guide/account-teams/teams.njk b/docs/user-guide/account-teams/teams.njk index 67fbc78187..f3fdcc798f 100644 --- a/docs/user-guide/account-teams/teams.njk +++ b/docs/user-guide/account-teams/teams.njk @@ -1,6 +1,6 @@ --- title: Teams -order: 2 +order: 3 desc: Manage teams and roles with Penpot's collaboration features! Learn how to manage teams, roles (Viewer, Editor, Admin, Owner), send invites and use webhooks. ---