- Concept
- Version · 6.0.2
- Manage
How access works without configurable permissions
Last updated: November 17, 2026
When your license does not include configurable permissions, every workspace has two fixed groups, Administrators and Members, and group membership is the only access setting. This helps you bring a team in quickly, because people can start working as soon as they sign in and the only decision you make is who else should be an administrator.
This applies to a workspace on a Starter or Team license, a workspace whose license has expired, and a workspace with no license installed. Every new installation starts this way until a license that includes configurable permissions is imported.
Where new users land
The first person to sign in to a workspace joins Administrators. Everyone who joins after that joins Members, including people who sign in with single sign-on when no group mapping applies to them. Nobody waits for approval, so the Users page has only the All, Active and Deactivated tabs and no Pending tab.
When you invite someone, you enter only their name and email address. They join Members when they accept, and the Pending invitations card shows (lands in Members) beside each invitation. You can move anyone to Administrators afterwards.
What you cannot change
The two groups are fixed. You cannot rename or delete them, change the permission template either group carries, or customize what that template grants. An administrator can move a Member to Administrators and back again, and that move is the only change to access you can make.
Because there is nothing else to configure, these parts of Liquibase Secure server are hidden:
The Groups and Permission Templates pages do not appear.
Connections and changelogs have no Access panel.
A project's Access tab shows only the Owners card, so you can still add and remove owners.
If someone opens one of these pages directly, or calls the API behind it, the page and the API response both read Configurable permissions are not included in your license.
What each group can do
Administrators can do everything in the workspace. They manage users and group membership, create service principals and their service tokens, view and revoke anyone's access tokens, view the system log, and archive or delete any project, connection or changelog, including ones they do not own.
Members can view all the data in the workspace and do most day-to-day work. They can create projects, connections and changelogs, edit connections and changelogs, and create and edit pipelines. They can also read every operation, including its raw logs, so a developer can investigate their own failed deployment without asking an administrator. Everyone in the workspace, Members included, can create their own personal access tokens to run Liquibase with their own access.
Owners keep full control of what they own. A Member who creates a project, connection or changelog can archive or delete it, but archiving or deleting anything else is for administrators.
The Users page and the License Management page carry this statement:
All members can view all data in this workspace, including raw operation logs. Upgrading to configurable permissions adds custom groups, permission templates and overlays, and lets you grant or deny access on individual projects, connections and changelogs.
Administrators can compare the two groups in the product by expanding What each group can do above the user list on the Users page.
What happens when you import a license that includes configurable permissions
When you import a Business or Enterprise license, the workspace activates configurable permissions. Activation converts the two groups so that you can edit them, and nobody's access changes. The groups change in these ways:
Members keeps its name and its members, and becomes an ordinary group that you can rename, delete and edit. It now carries the Platform/DevOps template across the workspace, plus a generated overlay that reproduces what Members could do before.
Administrators stays a system group, so you still cannot rename or delete it. Its template assignment, its overlay and its membership become editable.
A dialog titled Configurable permissions are now available confirms the change. It states that the effective permissions of every user were checked before and after the conversion and are identical, so you do not need to do anything.
From then on you can create your own groups, assign permission templates, customize them with overlays, and grant or deny access on individual projects, connections and changelogs. The workspace does not go back to two fixed groups, even if the license later ends.
If activation cannot complete
Before it applies anything, activation checks that converting Members would leave everyone's access exactly as it was. If the conversion would change someone's access, nothing is applied. A dialog titled Activation stopped lists each user whose access would have changed and what they would have lost or gained, and asks you to contact Liquibase Support. The failed check is recorded in the system log, and the License Management page reads Configurable permissions could not be activated: converting Members would have changed someone's access, so nothing was applied and everyone's access is unchanged. Contact Liquibase Support.
The license stays imported and the workspace keeps its two fixed groups. Activation runs again the next time you import a license or re-verify the current one.
What happens when the license term ends
Before a license that includes configurable permissions ends, the Groups, Permission Templates and Users pages show a banner with the date the term ends. By default the banner appears 90 days before that date, and the LIQUIBASE_PLATFORM_LICENSE_COMPLIANCE_EXPIRATION_NOTICE_DAYS environment variable changes how early it appears. Until the term ends, nothing about access changes.
When the term ends, the access model is frozen as it is configured. Nothing is deleted, every group, template, overlay, grant and deny is still enforced, and nobody's access changes. The banner then reads Access is frozen as configured, and you can view the model without editing it:
The Groups and Permission Templates pages stay visible and read-only.
You can still invite people. The invite dialog offers no group, and the person lands in Pending until the license is renewed. An invitation sent through the API can name only Administrators.
You can still move someone into or out of Administrators, and they keep every other group they are in. Someone moved out of Administrators joins Members if that group still exists. Someone moved in from Pending holds Administrators alone.
Apart from a move into Administrators, people waiting in Pending stay there until the license is renewed.
To edit access again, import a renewed license on the License Management page, which the banner's License Management button opens. Renewal makes the model editable again without creating or deleting anything.
How to tell which state a workspace is in
The Permissions row on the License Management page shows the workspace's state:
included · model configured means the license includes configurable permissions and they are active.
not included · model seeded means the workspace has the two fixed groups this article describes.
not included · model frozen means the license has ended and the access model is read-only.