ControlTokenOwnerMode

Controls the mode of Control Token ownership according to the following possible values. If the related property, ControlTokenCanOnlyRemoveOwnToken, is set to 1 then users may not be able to release tokens that they created, depending on the value of this property.

0 -> Session ID ownership

Users will only own tokens that have been applied during a given session, where "session" means a unique sign-in. If the user also signs in at a different workstation or via a thin client, that counts as a different session and they will not own the tokens from the first session. Further, if tokens are not configured to release automatically when the user signs out, then the act of signing out and signing back in will mean that the user no longer owns the original Control Tokens because those belong to the earlier session, not directly to the user.

1 - > Account ID ownership

This is the most straightforward ownership mode. Ownership is defined by the account id that requested the token. If the same user is logged into several machines their ownership of the Control Tokens extends across all machines.

2 -> Machine ID ownership

In this mode, ownership is defined by the machine ID. This is useful way to segregate release permissions based on physical workstations.

3 -> Custom Hook ownership

Ownership is defined by a custom hook that must be written by the customer, ControlTokenIsOwnerHook.SRC.

Creation of a custom hook is an advanced scripting task. Details are provided in Hooks for Control Tokens.