How licences work across subscriptions
Use a single licence to allow users to collaborate across projects in different SHIP-HATS subscriptions — no duplicate costs or extra subscriptions needed.
How access works: A licence allows a user to log in to a tool. To access a specific project, the user must also be added to the relevant tool resource (for example, a GitLab group, Jira project, or Confluence space) with an appropriate role.
Key takeaways
- Subscriptions provide licences, not project access.
- Users are assigned one licence per tool through a subscription.
- A single licence allows a user to work across projects in multiple subscriptions.
- Access to project/space/group/application is granted through tool resources and roles (for example, GitLab groups, Jira projects, Confluence spaces).
- Removing a user from a tool resource removes project/space/group/application access only — the licence is retained.
- Removing a licence removes access to all projects for that tool.
Core principle
A single licence per tool allows a user to work across multiple subscriptions.
You do not need to assign multiple licences or subscriptions for the same user.
How licences and subscriptions relate
In SHIP-HATS, users are not added to subscriptions directly. Instead:
- Users are assigned a licence through a subscription.
- A user holds one licence per tool, funded by a single subscription.
- The same licence can be used across projects in multiple subscriptions.
How access is granted across subscriptions
Access to project/space/group/application is managed by tool resources.
To work on a project in another subscription:
- The user must have the required licence
- The user must be added to the relevant tool resource such as project/space/group/application.
- An appropriate role must be assigned
For steps, see:
How access is removed
User access depends on what is removed:
| Action | Result |
|---|---|
| Remove user from a tool resource | User loses access to that specific tool resource such as project/space/group/application |
| Remove user’s licence | User loses access to all project/space/group/application for that tool |
Best practices
- If your subscription provisioned the licence to a user, before removing the licence, inform user your plan to remove the licence.
- If user still needs the licence to access tool resources in other SHIP-HATS subscriptions, this user should then coordinate with the Subscription Admin of the other subscription to provision them a licence via the latter subscription. This will maintain their access to tool resources across other subscriptions.
