Assigning Subscription Requests

When you create a subscription, you can optionally identify a default assignee for the requests generated by that subscription, as well as alternate assignees if the default assignee is out of the office.

The assignee is added to the target subscription requests as the request creator. This enables assignees to view and modify draft requests that are assigned to them.

You can assign users as the default assignee, and users or groups as alternate assignees. For groups, at least one person in the group must have complete Participant (Write) permission (all actions allowed and all properties able to be edited) on the dimension in the target viewpoint in order for the group to be assigned.


If you select a group as an alternate assignee, when subscription requests are generated, they are assigned one by one to the available members of the group that have the appropriate permissions until all available members of the group have been assigned a request. A user is not a repeated until all valid members of the groups have been assigned a request in the latest round of assignment. Then, the assignment starts over with the first available group member again.

Enable the Collaborate option to add alternate assignees who are not currently assigned a request as collaborators. This enables them to make changes to request items and add comments or attachments. See Creating, Editing, and Validating Subscriptions.

Assignee Priority

Users and groups are assigned to subscriptions in this order:

  1. The request is always assigned to the default assignee if the assignee is available and has the appropriate permissions.
  2. If the default assignee is out of the office (see Setting Your Preferences) or does not have appropriate permissions, the request is assigned to the users listed in the alternate assignees as follows:
    1. Request assignment begins with the first user listed in the alternate assignees and continues down the list of alternate assignees.
    2. If an alternate assignee is out of the office or does not have sufficient permissions, the request is assigned to the next alternate in the list.
    3. After all valid users in the alternate assignee list have been assigned a request, the current assignment round is considered completed and the next round of assignments is initiated.


      If a user is listed multiple times in the alternate assignees (for example, if a user is listed as an alternate assignee and is also part of a group that is listed as alternate assignees), the user is assigned a request only one time per assignment round.

If you assign a default assignee but no alternate assignees and the default assignee is not available, the request is assigned to the default assignee so that it can be worked when the default assignee is back in the office. If you assign alternate assignees but not a default assignee and none of the alternates are available, then the subscription is skipped and a notification is sent to the subscription owner.


The subscription request assignee does not need any permissions on the source viewpoint.

Assignees receive email notifications when the request in the source viewpoint is submitted. See Request Notifications.