LetsGo maintains several categories in the database to support the functionality that comes with the platform. This describes those built-in categories.
Key: {tenantId}
Stores information about a tenant in the system, including the current subscription plan and Stripe subscription information, if any. Tenants that have been logically deleted remain in the database but are marked as deleted.
Key: {identityId}
Stores user profile associated with a specific identity (a credential the user used when logging in to the system using Auth0). This profile is used by the UI components of the web responsible for the user management features to display a descriptive name of users in the UI.
Key: /{tenantId}/{identityId}
Represents membership of a user {identityId} in tenant {tenantId}. This is used by the UI components of the web responsible for the user management features of a tenant.
Key: /{identityId}/{tenantId}
Represents the tenants the user {identityId} has permissions to access. This is used to efficiently query which tenants a logged in user has access to and manifests itself in the UI of the web component as a tenant selector drop-down. It is directly used by the /v1/me endpoint of the API component to return all tenants the caller of the API has access to.
Key: {issuerId}
Represents a trusted issuer registered in the system.
Key: / (a fixed value of a singleton item)
There is only ever up to one such item in the database. It specifies which of the PKI trusted issuers registered in the system is the active issuer.
Key: /{tenantId}/{invitationId}
Stores an invitation to join a tenant. Unused invitations expire after 24h.
Key: varies
This category is used by LetsGo tests.