Tenancy Groups User Roles Resources Teams Integrations
- Shannon Farguson
- Matthew Hall
In plain language this product needs to:
Allow product teams the ability to designate which members of their team are permitted to change the configuration of their product
Hold the configuration of a product’s connections to digital services external to its own control
Page Contents:
Overview:
Tenancy Strategy Workshop 2024-08-30
Information Architecture of the Tenancy Strategy (access management model)
A tenant consists of a
registration and approval of an initiative/program area/application
users with roles in an initiative/program area/application
registration and integration with services/resources/common components
groups with
roles available from the registered and approved list of integrated services/resources/common components
users who as members of the group will have those roles assigned when they log into services
resources/services/common components categories include
infrastructure product
administrative registration services
saas/cots
common hosted user capabilities
accounts
for gatekeeping whether to allow someone to do something by checking roles or other jwt attributes
for a way to collect attributes sent with their login or verified from a digital credential
rules