Introduction
Last updated
Last updated
Quasr supports multi-tenancy that various business scenarios rely upon. You can read up on the multi-tenancy concept here.
A Quasr customer can own multiple tenants. Technically there is no limitation of the number of tenants that can be provisioned by a customer and under a customer's subscription plan. The free-tier, as part of all subscription plans, includes up to three tenants for free, while additional tenants are charged.
Each tenant comes with a Tenant Administration UI, which is documented in this section.
The user interface allows to manage the following elements, as can be seen from the left-hand main navigation:
Dashboard: See near-real-time statistics about the tenants usage. The metrics "Monthly Active Accounts" (MAA) and "Monthly API Calls" (MAC) are displayed here.
Tenant Settings: Change the tenant label or color code, expiration settings for sessions, accounts, tenant.
Your Security: Manage the authentication methods (factors) of your own account, which you use to log into the tenant administration of the currently selected tenant.
Entities:
Accounts: See all accounts (these can be human users or machine clients) and manage them by creating, editing, deleting them from here.
Factors: Configure allowed authentication factors for the tenant.
Controls: Configure Scope and Legal Controls, related to Consent Management
Extensions: allows custom code to be executed (Node.js on Lambda) to add custom claims to ID and/or access tokens or respond to platform events (eg. OTP or account creation)
Events: here you can see the latest 100 events on your tenant
APIs: Information about available APIs as well as your current Personal Access Token
Your resources can be in any of the below states:
PENDING means the resource is currently not yet ready and some action still needs to happen, such as validating a factor enrollment, or a code extension that is still being build and deployed. Generally PENDING items will expire quickly.
ENABLED means the resource is good for use. Generally ENABLED items will take much longer to expire and expiry is related to inactivity.
DISABLED means the resource can't be used - but it can still be re-enabled whenever desired.
LOCKED means the resource can't be used and it is not possible to re-enable it. Such state can arise because a parent resource has been disabled or locked, but it can also indicate that it has been locked by us in rare circumstances.
