Use

By default, Dec 31, 9999 is assigned as the valid-to date when you add a new user or team. If you want to limit the access that is given by the authorization context to a certain time period, adjust the Valid-to date correspondingly.

After triggering the workflow, the approver gets a notification in the My Inbox app about the task so that they can approve or reject the request.

After you select a specific folder, use this field to restrict the activities that users can perform on the business objects in that folder to the following:
  • Create

  • Read

  • Update

  • Delete

  • Inherit Authorization

    Note

    This is currently available only for product folders and subfolders.

You can add multiple activities to the same folder.

Use

Use this restriction method to control user access to product structures within a specific folder.

For example, you can give read access to product structures in folder 0099, and to the product structures in folder 0088. Users who are restricted by the authorization context can view product structures in both folders.

Dependencies
When you create an authorization context, you can use any of the following methods for restricting access in the same authorization context:
  • Use only object attribute types.

  • Use only authorization group types.

  • Use only business object restrictions.

  • Use a combination of the available methods.

After you select an object attribute type and the relevant attributes, use this field to restrict the activities that can be performed on objects with those attributes to the following actions:
  • Create

  • Read

  • Update

  • Delete

You can add multiple activities to the combination of object type and selected attributes.

Use

When you create a new authorization group, a name is assigned that comprises the authorization group type and a number in parentheses. This name is automatically generated. You can't change it.

Use

You can control user access using one or more authorization groups. The currently available authorization group restricts access by combining BOM usage and the plant or specification type and product category object attribute types.

The access restriction between the object attribute types in an authorization group has an AND relationship. If, for example, you create an authorization group in which you give read access when the plant is Plant 001 and the BOM usage is 1 (Production), the users restricted by that authorization context can only view product structures that are assigned to Plant 001 and have production as the BOM usage.

Dependencies
When you create an authorization context, you can use any of the following methods for restricting access in the same authorization context:
  • Use only object attribute types.

  • Use only authorization group types.

  • Use only business object restrictions.

  • Use a combination of the available methods.

Use this app to create authorization contexts for controlling the access of users or groups of users (teams) to specific business objects that are part of the Enterprise Product Structure, Product Handover, Specification Management, Formulation, Document Management, or Product Data Integration SaaS applications.

Key Features

This app lets you do the following:

  • Create authorization contexts to give users access to specific business objects, such as product structures or particular properties of a specification, or a recipe type.

  • Create authorization contexts to allow users to perform specific actions on the business objects that they can access.

  • Assign authorization contexts to specific users or teams.

You can enable or disable property-based authorization for each of your authorization contexts. By default, property-based authorization is disabled.
  • Property-based authorization is disabled: this means that users and user groups added to the respective authorization context have access to all properties within the defined specification types and product categories.

  • Property-based authorization is enabled: this means that users and user groups added to the respective authorization context have access to only those properties that are explicitly added to the context.

To enable property-based authorization, go to Edit mode and choose Enable Property-Based Authorization.

After the functionality is enabled, you can add properties to your authorization context. Users added to the context will only see these added properties, in the context of the specified specification types and product categories. You can find details of property based authorization in Property-Based Authorization for Specification Management.

The restriction for property visibility affects all apps of the Specification Management SaaS Application.

Use the value help for this filter to select a user. The list is then filtered to display the authorization contexts to which the user is assigned. If the user is part of a team, the results list also includes authorization contexts that are assigned to teams to which the user belongs.

Use the value help for this filter to select a team. The list is then filtered to display the authorization contexts to which the team is assigned.

Use
You can add different combinations of different types of object attributes and activities to an authorization context. The relationship between the different object attribute types in the same authorization context is an OR relationship.
Example You make two entries for object attribute types in your authorization context:
  • You give read access to all business objects assigned to Plant 00001.

  • You give read access to all BOMs that have Engineering as their BOM usage.

The users that you assign to this authorization context then have access to all BOMs assigned to Plant 00001 and all BOMs with Engineering as their BOM usage, regardless of their plant assignment.
Dependencies
When you create an authorization context, you can use any of the following methods for restricting access in the same authorization contexts:
  • Use only object attribute types.

  • Use only authorization group types.

  • Use only business object restrictions.

  • Use a combination of the available methods.

Use

You can add multiple attribute values in the same row and then assign the relevant activities to this combination.

Note

If you have group BOMs and want to restrict user access to them, enter "" (double quotation marks) as the Plant value in this column. Then select the relevant activities.

After you select an authorization group type and the relevant attribute values, use this field to restrict the activities that can be performed on objects with those attributes to the following actions:
  • Create

  • Read

  • Update

  • Delete

You can add multiple activities to the authorization group. You can only add the same activities to both authorization group types within an authorization group.

Dependencies
The users that you assign here must also have roles that are based on role templates specific to authorization contexts for the integrated SaaS applications. The role templates provide access to the relevant apps. The authorization context restricts the access to the business objects that users can work on in those apps. For more information, see:
Prerequisites

To restrict the access of a group of users, create a team using the Manage Teams (New) app and assign the team to an authorization context.

Dependencies
The users in the team must also have roles that are based on role templates specific to authorization contexts for the integrated SaaS applications. The role templates provide access to the relevant apps. The authorization context restricts the access to the business objects that users can work on in those apps. For more information, see: