Set Admin Permissions via the Database

Available from Version: 9.7

Hosting Option: Corporate Cloud

Required Permissions: IT Admin

If you are not hosting in the empower® Cloud, you need to set the admin permissions yourself via the empower® Database.

If you are hosting in the empower® Cloud, empower® Support makes these changes for you.

Note

If you are hosting in the empower® Cloud and want to assign admin permissions to a new user, contact empower® Support.

Except for the Customizing Admin, all admin roles need to be set via the database.

The Customizing Admin can be set via the empower® Admin Center, but it can also be set via the database.

Note

For further information regarding the management of Customizing Admins, see Manage Customizing Admins.

For further information regarding the admin roles in empower®, see Admin Roles in empower® .

For further information regarding admin permissions for empower® Document Automation, see Assign Admin Permissions for empower® Document Automation.

Set Global Admin Permissions >= 9.7 (Customizing Admin, Content Admin)

To set the global admin permissions which apply to all empower® Components, follow the following steps:

  1. To find the user you want to assign admin permissions to, use the following SQL statement:

    SELECT TOP (50) *
FROM [core].[PrincipalUsers]
WHERE LastName = 'UserName' --> the name of the user

    To find the group you want to assign admin permissions to, use the following SQL statement:

    SELECT TOP (50) *
FROM [core].[PrincipalGroups]
WHERE Name = 'GroupName' --> the name of the group

  2. Copy the principal ID.

  1. Navigate to the folder Programmability and select the subfolder Stored Procedures.

  2. Right-click on core.spAddAdminUserPrincipalId.

    A context menu opens.

  3. Choose the option Execute Stored Procedure….

    A dialog box opens.

  1. In the row PrincipalId, enter the copied principal ID of the user into the column Value.

  2. Now, you can grant the required admin permissions:

    1. If you want to grant Content Admin permissions to the specified user, enter the value 1 for the row IsContentAdmin in the column Value.

      If you do not want to change the user's permissions regarding this role, leave the value 0.

    2. If you want to grant Customizing Admin permissions to the specified user, enter the value 1 for the row IsCustomizingAdmin in the column Value.

      If you do not want to change the user's permissions regarding this role, leave the value 0.

  3. Click on the button OK.

  4. Repeat the entire process for all users that you want to grant the respective admin permissions to.

Figure 1. Fill in Stored Procedure for Global Admin Permissions

Fill in Stored Procedure for Global Admin Permissions

After the next automatic or manual synchronization, the specified user should now have the required permissions.

Note

If a user has already been granted the respective admin permissions, setting the value to 0 does not remove these permissions but leaves the current status.

Note

Using the stored procedure, you can only assign the permissions to one user at the same time.

Alternatively, you can assign the permissions to a user group.

Set Global Admin Permissions <= 9.6 (Corporate Design Admin)

In versions lower than version 9.7, there is only one global admin role which is called Corporate Design Admin.

To set the global admin permissions which apply to all empower® Components, follow the following steps:

  1. To find the user you want to assign admin permissions to, use the following SQL statement:

    SELECT TOP (50) *
FROM [core].[PrincipalUsers]
WHERE LastName = 'UserName' --> the name of the user

    To find the group you want to assign admin permissions to, use the following SQL statement:

    SELECT TOP (50) *
FROM [core].[PrincipalGroups]
WHERE Name = 'GroupName' --> the name of the group

  2. Copy the principal ID.

  1. Navigate to the folder Programmability and select the subfolder Stored Procedures.

  2. Right-click on core.spAddAdminUserPrincipalId.

    A context menu opens.

  3. Choose the option Execute Stored Procedure….

    A dialog box opens.

  1. In the row PrincipalId, enter the copied principal ID of the user into the column Value.

  2. If you want to grant Corporate Design Admin permissions to the specified user, enter the value 1 for the row IsCDAdmin in the column Value.

    If you do not want to change the user's permissions regarding this role, leave the value 0.

  3. Click on the button OK.

  4. Repeat the entire process for all users that you want to grant the respective admin permissions to.

After the next automatic or manual synchronization, the specified user should now have the required permissions.

Note

If a user has already been granted the respective admin permissions, setting the value to 0 does not remove these permissions but leaves the current status.

Note

Using the stored procedure, you can only assign the permissions to one user at the same time.

Alternatively, you can assign the permissions to a user group.

Set Admin Permissions for Word and Outlook

To set the admin permissions which apply to the empower® Components for Word and Outlook, follow the following steps:

  1. To find the user you want to assign admin permissions to, use the following SQL statement:

    SELECT TOP (50) *
FROM [core].[PrincipalUsers]
WHERE LastName = 'UserName' --> the name of the user

    To find the group you want to assign admin permissions to, use the following SQL statement:

    SELECT TOP (50) *
FROM [core].[PrincipalGroups]
WHERE Name = 'GroupName' --> the name of the group

  2. Copy the principal ID.

  1. Navigate to the folder Programmability and select the subfolder Stored Procedures.

  2. Right-click on dbo.spAddDocsMailsSheetsAdminUserPrincipalId.

    A context menu opens.

  3. Choose the option Execute Stored Procedure….

    A dialog box opens.

  1. In the row PrincipalId, enter the copied principal ID of the user into the column Value.

  2. Now, you can grant the required admin permissions:

    1. If you want to grant Mails Campaign Admin permissions to the specified user, enter the value 1 for the row IsMailsCampaignAdmin in the column Value.

      If you do not want to change the user's permissions regarding this role, leave the value 0.

    2. If you want to grant Mails Customizing Admin permissions to the specified user, enter the value 1 for the row IsMailsCustomizingAdmin in the column Value.

      If you do not want to change the user's permissions regarding this role, leave the value 0.

    3. If you want to grant Signature Template Admin permissions to the specified user, enter the value 1 for the row IsTemplateSignatureAdmin in the column Value.

      If you do not want to change the user's permissions regarding this role, leave the value 0.

    4. If you want to grant Company EAV Admin permissions to the specified user, enter the value 1 for the row IsCompanyEavAdmin in the column Value.

      If you do not want to change the user's permissions regarding this role, leave the value 0.

    5. If you want to grant EAV Editor Admin permissions to the specified user, enter the value 1 for the row IsEavEditorAdmin in the column Value.

      If you do not want to change the user's permissions regarding this role, leave the value 0.

  3. Click on the button OK.

  4. Repeat the entire process for all users that you want to grant the respective admin permissions to.

Figure 2. Fill in Stored Procedure for Word and Outlook Admin Permissions

Fill in Stored Procedure for Word and Outlook Admin Permissions

After the next automatic or manual synchronization, the specified user should now have the required permissions.

Note

If a user has already been granted the respective admin permissions, setting the value to 0 does not remove these permissions but leaves the current status.

Note

The stored procedure in the empower® Database contains some permissions that are deprecated and are not required anymore.

The deprecated permissions are the following:

  • DocsConsistencyCheckAdminPermission

  • LinkButtonIconAdminPermission

  • StyleAdminPermission

You do not need to set these permissions when using the stored procedure.

Note

Using the stored procedure, you can only assign the permissions to one user at the same time.

Alternatively, you can assign the permissions to a user group.

Was this article helpful?

/

Comments

0 comments

Article is closed for comments.