Tenant creation by SARA
Create, query and configure tenants throughSARA of Support.
The process of creating tenants bySARA starts by creating a request, if the tenant has already been created by Senior Digital, the auto-tenant complements the process with the generation of the Shovel and SAML/ADFS certificate, and sends the data to the tenant requestor automatically. Additional tenant data can only be sent once for security reasons. If the tenant does not yet exist, the auto-tenant waits until it is created by a developer to continue the process.
To learn more about what a tenant is and how it works, access the documentation onTenant Management on senior X Platform.
What can you do:
Consult tenants
AccessSARA and sign in with the requester user in Zendesk. Select the optionTENANTS, click inI would like to consult a tenant and enter the desired domain to make the query.
Information provided about the tenant:
- Tenant name: domain without dots;
- Tenant domain: tenant domain;
- Status: Active, Inactive;
- Ready to use: Yes, No;
- Authentication types: G5/G6, G7, SAML/ADFS and LDAP.
The e-mail and platform login of the tenant requestor, and administrators 1 and 2 will also be presented in the Contact information.
Request tenant creation
AccessSARA, log in with the requester user in Zendesk, select the optionTENANTS and clickI would like to request the creation of a tenant. It is necessary to fill in the following fields to check the tenant's availability:
- Customer's corporate name;
- Customer code;
- CNPJ of the customer;
- Authentication type;
- Account Type;
- Customer domain.
If it already exists in an informed environment (production, approval, demonstration and development), an error message will be displayed, not allowing the request to continue.
This request first arrives at theSenior Digital, which starts creating the requested tenant. After creation, the requester and administrators will receive an email with the tenant administrator password. If the optionConfirm Email is selected, the tenant will only be created after confirmation by one of the administrators. The administrators' emails entered in the form must have the same domain as the tenant to be created.
A tenant creation request is created, so that the SAML certificate is sent to the requestor and administrators, and the certificate is configured in Shovel.
Request tenant product configuration
AccessSARA and sign in with the requester user in Zendesk. Select the optionTENANTS, click inI would like to request the configuration of a tenant and enter the desired domain to check if the tenant exists on the platform. During configuration, it is necessary to inform again the account types (production, approval, demonstration and development) and the products to be configured.
A tenant configuration request is created that presents all the fields entered in the form, to configure the products in the tenant and then return to the requestor's email.
Tenant configuration process by systems:
HCM
To enable integration with HCM modules, the self-tenant checks whether the product, HCM, is enabled for that tenant (integrating with the HCM API).
If the HCM tenant does not exist, the auto-tenant issues the request to create the tenant, informing the requested modules. HCM creates the tenant as requested at creation, and sends the HCM integrator key file (.pem) via email to the tenant requestor. The self-tenant sends a message warning that the HCM modules have been enabled.
If the HCM tenant already exists, the self-tenant compares the HCM modules with the requested ones, adding the requested modules to the existing ones and changing the authentication type as requested. HCM changes the tenant as requested during creation, the self-tenant sends a message notifying that the HCM modules have been enabled. Additional tenant data can only be sent once for security reasons.
Senior round
To enable integration with Ronda senior X modules, the self-tenant checks whether the product, Ronda senior X, is enabled for that tenant (integrating with Ronda senior X API/platform).
If the Ronda senior X tenant does not exist, the self-tenant issues the request to create the tenant and Ronda senior X creates the tenant generated by the product, as requested during creation. Then, the auto-tenant sends a message warning that the Ronda senior X modules have been enabled.
If the tenant already exists, the self-tenant issues the request to change the Ronda senior X tenant, and the system edits the tenant, as requested upon creation. The auto-tenant sends a message warning that the Ronda senior X modules have been enabled.
Account Creation
When creating an account ('createAccount') you must pay attention to two details:
- If 'tenantDomain' is null or equal to the domain entered in 'businessEmail', it must have a maximum of 32 characters.
- If the 'tenantDomain' entered is not null or is different from the domain entered in 'businessEmail', the system will automatically include the information 'seniorx' at the end, if this also exceeds 32 characters an exception will be triggered with the following message:The tenant domain ('informed in tenantDomain') must have a maximum of 32 characters.
Important
- Upon receipt of tenant creation documentation, it is recommended to create a second administrator user. This additional user would be created for security reasons, such as loss of the primary admin user's password, failure to reset passwords, and/or other issues involving the primary admin user.
- There is a period of 3 days after the request is opened in SARA for the tenant data to be received and the creation to be carried out. If you do not receive the email confirming the creation of the tenant within this period, first check your SPAM folder, and then contact support.
Note
The tenant administrator user has access to all tenant administration permissions, and is the responsibility of the customer. Senior is not responsible for damages caused if this password is shared with third parties. For this reason, we suggest changing the password after the first access, and to facilitate blocking in inappropriate cases, it is recommended to create nominal users for other users of the solution. In the case of the administrator user, the email must be updated so that, in the event of forgetting the password, it is possible for the administrator to recover it, without the need for any mediation from Senior.
To set a user as an administrator, go to the documentation onUser Management.
