You can assign users edit access to create and change a contract request (CR), or release access to create release orders against the contract. Only users with release access can select restricted catalog and non-catalog items.

If your Ariba Contract Compliance configuration contains different partitions, you can specify whether the contract can be accessed only from the current partition or from all partitions (a global contract). Note: When receiving items listed on a global contract, you must receive in the partition in which the contract was created.

Contract requests that have been created from Ariba Contract Workbench cannot be edited from Ariba Contract Compliance, only from Ariba Contract Workbench, for example, you cannot change the Edit Access section.

For contracts that do not require release orders, Release Access options are visible only if the contract supports direct invoicing.

Users must have either the CreateContract or ContractManager permission to be listed in the Edit Access chooser. A user whose name does not appear there can submit a personal profile change request for those permissions. After the request is approved, the user's name is listed in the chooser.

Release Access choosers contain individual selections for each partition in which a user exists, so you can be partition-specific when assigning release access for global contracts.

To assign edit access, click select and choose one or more users who are authorized to edit the contract request (CR).

To set release access:

• Click Current Partition only to create a contract that requires users to be logged into the current partition to create release orders against it. You can grant release access only to users who exist in the current partition.
• Click All Partitions (Global Contract) to create a global contract. You can grant selected users from any partition access to create release orders against the contract (from any partition).
• By default, the Restrict Release Access check box is unchecked, indicating unrestricted release access for the contract by all users (which applies to partitions in which the contract or global contract is accessible). Ariba Contract Compliance will automatically select an appropriate open contract (when one is available), and attach it to the requisition line item. Click the Restrict Release Access check box to restrict users' access, and then select specific user(s) who are authorized to create releases against the contract.
• When assigning release access for a global contract, some values (such as Role) exist in all partitions, and some values (such as User and Supervisor) exist on a per-partition basis:
  • If a chooser contains a single selection for a value such as Role (IS Manager, for example), select IS Manager once, and users in any partition who have that role are assigned release access.
  • If the chooser contains multiple selections for a value such as User or Supervisor (Beth Wilson, for example), you must select Beth Wilson for every partition in which she will have release access.

To remove a user who has been given edit or release access, return to the associated chooser and click Remove.