Managing tenants in Momentus Connect is a critical part of ensuring seamless onboarding, migration, and access control for both existing and new customers. This article explains the different ways tenants are created in Momentus Connect, what happens if a tenant is missed, and how users are assigned to tenants.
In Momentus Connect, tenant management is supported through:
- Pre-production migration: bulk creation of known tenants.
- Auto-provisioning: automatic creation of new tenants when accessed.
- (Planned) Daily batch jobs: ongoing synchronization of tenants.
- Granular tenant-level access control: flexible user-to-tenant assignment.
In this article:
Tenant provisioning
There are two main ways tenants (existing and new) are created in Momentus Connect, with a third option under development.
Pre-Production Migration
- For the initial setup, data was sourced from Elite and Enterprise DevOps systems.
- Using migration scripts, tenants and customers were created in bulk.
- As a result, most known tenants and customers with existing Salesforce accounts are already created (or will be created) in the corresponding Momentus Connect environment for launch.
Auto-Provisioning (On-Demand Creation)
If a tenant was missed during migration or if a new tenant is introduced later, auto-provisioning ensures users are not blocked from accessing Momentus Connect.
- When an unknown tenant accesses Momentus Connect, the system automatically provisions a new tenant.
- However, in such cases, a corresponding customer account may not exist yet. This situation results in what we call an orphan tenant. Handling of orphan tenants is explained further in the next section.
Daily Batch Job (Planned)
A third method of creating new tenants is being developed: a daily batch job.
- This job will check for new tenants created via auto-provisioning.
- It will then create them in the same way as the migration process.
At launch, the system relies on a one-time migration and auto-provisioning. Shortly after, the daily batch provisioning will be added to strengthen the process.
Orphan Tenants
An orphan tenant is created when a tenant is automatically provisioned in Momentus Connect without a corresponding customer account being created.
- These cases may require manual review and follow-up actions.
- Processes are being put in place to ensure orphan tenants are tracked and reconciled effectively.
Steps to Link Orphan Tenants to a Customer
Linking and unlinking tenants can only be done by super users. To link an orphan tenant:
- Navigate to Momentus Connect. As a super user, you will land on the Customer Selection Page.
- Search for and select the customer you are managing tenants for. The Customer Dashboard displays. From here you can link tenants for the customer.
- On the Tenants tab, click Link Tenant. The Link Tenant to Customer modal opens.
- Select the Product: Enterprise or Elite.
- In the Tenants field, a list of Orphan tenants displays. Select the tenant to link.
- Click Save.
User-to-Tenant Assignment
Assigning users to tenants is crucial for both security and usability. In Momentus Connect, this can happen in two ways:
Automatic Assignment
- If a user comes from a known tenant and is already authenticated, the system automatically assigns them to that tenant.
Manual Assignment
- Support users or super users can also manually assign users to specific tenants. See Manage Users in Momentus Connect for more information.
- This is particularly useful when a customer account contains multiple tenants. For example, a customer may have four tenants, but a user may be granted access to only two of them.
- This approach provides granular tenant-level access control. Granular tenant-level access allows customers to manage access more precisely. For example:
- Some customers do not allow all users to access test tenants.
- Others may want only specific admins to have access to certain tenants.
- This flexibility helps customers apply their own rules for who can access which tenants.
Comments
0 comments
Article is closed for comments.