Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

All cloud instances are provisioned with a TenantAdmin user by default. This user can be utilized within the cloud environment just like any other Square9 User. If desired, this user can be replaced but the user which replaces the TenantAdmin must have specific rights made available to it and must be referenced appropriately in certain areas of the environment. This knowledge base article will cover those rights/locations.

Standalone GlobalSearch:

Requires no special considerations, beyond actively ensuring that an account is provisioned with full admin rights to the application prior to the removal of the TenantAdmin user. This can be achieved by granting membership to the GS Cloud Admin group.

Standalone GlobalSearch with GlobalAction:

Ensure that an account is provisioned with full admin rights to the application prior to the removal of the TenantAdmin user. This can be achieved by granting membership to the GS Cloud Admin group.

Notify support team of the new admin user’s name, support can then request that cloud update the references on the backend of the application as appropriate.

Standalone GlobalCapture:

Ensure that an account is provisioned with full admin rights to the application prior to the removal of the TenantAdmin user. This can be achieved by granting membership to the GS Cloud Admin group.

Update portals with new admin user.

GlobalSearch with GlobalCapture:

Ensure that an account is provisioned with full admin rights to the applications prior to the removal of the TenantAdmin user. This can be achieved by granting membership to the GS Cloud Admin group.

Update portals with new admin user.

GlobalSearch/GlobalAction with GlobalCapture:

Ensure that an account is provisioned with full admin rights to the applications prior to the removal of the TenantAdmin user. This can be achieved by granting membership to the GS Cloud Admin group.

Update portals with new admin user.

Notify support team of the new admin user’s name, support can then request that cloud update the references on the backend of the application as appropriate.

  • No labels