Configuring New User Registration Jobs

Astoria comes with basic building blocks to configure new user registration jobs. An administrator can update different repository objects to customize the configuration for your environment.

Tip: Many building blocks used in the new user registration job are similar to those used in a workflow. However, workflows rely on a sequence of jobs progressing through status changes. The new user registration job is a one-step job.
  1. Create a Role to identify the administrators who are the audience for the new user registration jobs.
    This role is not permanently assigned to users or groups. Instead, the participants for the role are identified at appropriate levels of hierarchy in the repository.
    1. Right-click Role Definitions and select Create > New Role.
      The New Role dialog appears.
    2. Enter a Name for the role.
      For example, New User Registration.
    3. Enter a Description for the role.
      For example, Administrators who process New User Registration jobs.
    4. Do not select capabilities for the General Privileges, Custom Attributes, or Annotations tabs.
    5. Click OK.
    The role definition is saved in the repository.
  2. Edit the New User Registration Audience webform, found in the Administration cabinet.
    1. In the Audience Role field, select the role name you created in the previous step.
    2. If needed, adjust other fields in the webform.
      Most organizations will not need to make other changes. For details about the additional fields, see Audience Parameters Document Fields.
      Note: The webform uses only one job ticket, thus only one Job Audience Parameters repeat group entry.
    3. Scroll to the top or bottom of the webform and click Checkin Document.
    4. When prompted, provide a checkin note indicating what was changed in the webform, then click OK.
  3. [Optional] Create one or more groups to include the administrator users who will process requests.
    The group name and description should clearly indicate the purpose of the group.
  4. Specify the users or groups to identify administrators as the audience for new user registrations, using access controls.
    You can set the access controls at different levels in the repository hierarchy, corresponding with the scope of responsibility for the administrators who process requests. If all requests will be processed by the same administrators, you can set the access controls at the Global or Backstop level. See Global and Backstop Access Controls. You can also set the access controls at a cabinet or folder level, with different sets of administrators corresponding with different projects.
    1. Select the hierarchy level and issue the Define Access Controls command.
      • For Global or Backstop levels, in the Workbench Ribbon, select the Administration tab, then from the Security band, select Global Access Controls or Backstop Access Controls.
      • For cabinet or folder levels, right click the cabinet or folder and select Administration > Define Access Controls.
      The Define Access Controls dialog appears.
    2. Select the Roles tab.
    3. In the Role Groups area, move the role name you created above from the Available list to the Present list.
    4. Select the role name in the Present list, then in the Details area, move either user names or the group name you created earlier from the Available list to the Present list.
    5. Click OK.
  5. Test the New user registration option to ensure it works correctly.
    See Requesting a User Registration. Adjust any of the building blocks if necessary.