azuread.AccessPackageAssignmentPolicy

The ID of the access package that will contain the policy.

The description of the policy.

The display name of the policy.

An approval_settings block to specify whether approvals are required and how they are obtained, as documented below.

An assignment_review_settings block, to specify whether assignment review is needed and how it is conducted, as documented below.

How many days this assignment is valid for.

The date that this assignment expires, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z).

Whether users will be able to request extension of their access to this package before their access expires.

One or more question blocks for the requestor, as documented below.

A requestor_settings block to configure the users who can request access, as documented below.

The ID of the access package that will contain the policy.

The description of the policy.

The display name of the policy.

An approval_settings block to specify whether approvals are required and how they are obtained, as documented below.

An assignment_review_settings block, to specify whether assignment review is needed and how it is conducted, as documented below.

How many days this assignment is valid for.

The date that this assignment expires, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z).

Whether users will be able to request extension of their access to this package before their access expires.

One or more question blocks for the requestor, as documented below.

A requestor_settings block to configure the users who can request access, as documented below.

The ID of the access package that will contain the policy.

The description of the policy.

The display name of the policy.

An approval_settings block to specify whether approvals are required and how they are obtained, as documented below.

An assignment_review_settings block, to specify whether assignment review is needed and how it is conducted, as documented below.

How many days this assignment is valid for.

The date that this assignment expires, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z).

Whether users will be able to request extension of their access to this package before their access expires.

One or more question blocks for the requestor, as documented below.

A requestor_settings block to configure the users who can request access, as documented below.

The ID of the access package that will contain the policy.

The description of the policy.

The display name of the policy.

An approval_settings block to specify whether approvals are required and how they are obtained, as documented below.

An assignment_review_settings block, to specify whether assignment review is needed and how it is conducted, as documented below.

How many days this assignment is valid for.

The date that this assignment expires, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z).

Whether users will be able to request extension of their access to this package before their access expires.

One or more question blocks for the requestor, as documented below.

A requestor_settings block to configure the users who can request access, as documented below.

The ID of the access package that will contain the policy.

The description of the policy.

The display name of the policy.

An approval_settings block to specify whether approvals are required and how they are obtained, as documented below.

An assignment_review_settings block, to specify whether assignment review is needed and how it is conducted, as documented below.

How many days this assignment is valid for.

The date that this assignment expires, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z).

Whether users will be able to request extension of their access to this package before their access expires.

One or more question blocks for the requestor, as documented below.

A requestor_settings block to configure the users who can request access, as documented below.

The ID of the access package that will contain the policy.

The description of the policy.

The display name of the policy.

An approval_settings block to specify whether approvals are required and how they are obtained, as documented below.

An assignment_review_settings block, to specify whether assignment review is needed and how it is conducted, as documented below.

How many days this assignment is valid for.

The date that this assignment expires, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z).

Whether users will be able to request extension of their access to this package before their access expires.

One or more question blocks for the requestor, as documented below.

A requestor_settings block to configure the users who can request access, as documented below.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

Whether an approval is required.

Whether an approval is required to grant extension. Same approval settings used to approve initial access will apply.

An approval_stage block specifying the process to obtain an approval, as documented below.

Whether a requestor is required to provide a justification to request an access package. Justification is visible to approvers and the requestor.

Whether an approval is required.

Whether an approval is required to grant extension. Same approval settings used to approve initial access will apply.

An approval_stage block specifying the process to obtain an approval, as documented below.

Whether a requestor is required to provide a justification to request an access package. Justification is visible to approvers and the requestor.

Whether an approval is required.

Whether an approval is required to grant extension. Same approval settings used to approve initial access will apply.

An approval_stage block specifying the process to obtain an approval, as documented below.

Whether a requestor is required to provide a justification to request an access package. Justification is visible to approvers and the requestor.

Whether an approval is required.

Whether an approval is required to grant extension. Same approval settings used to approve initial access will apply.

An approval_stage block specifying the process to obtain an approval, as documented below.

Whether a requestor is required to provide a justification to request an access package. Justification is visible to approvers and the requestor.

Whether an approval is required.

Whether an approval is required to grant extension. Same approval settings used to approve initial access will apply.

An approval_stage block specifying the process to obtain an approval, as documented below.

Whether a requestor is required to provide a justification to request an access package. Justification is visible to approvers and the requestor.

Whether an approval is required.

Whether an approval is required to grant extension. Same approval settings used to approve initial access will apply.

An approval_stage block specifying the process to obtain an approval, as documented below.

Whether a requestor is required to provide a justification to request an access package. Justification is visible to approvers and the requestor.

Maximum number of days within which a request must be approved. If a request is not approved within this time period after it is made, it will be automatically rejected.

Whether alternative approvers are enabled.

A block specifying alternative approvers when escalation is enabled and the primary approvers do not respond before the escalation time, as documented below.

Whether an approver must provide a justification for their decision. Justification is visible to other approvers and the requestor.

Number of days before the request is forwarded to alternative approvers.

A block specifying the users who will be asked to approve requests, as documented below.

Maximum number of days within which a request must be approved. If a request is not approved within this time period after it is made, it will be automatically rejected.

Whether alternative approvers are enabled.

A block specifying alternative approvers when escalation is enabled and the primary approvers do not respond before the escalation time, as documented below.

Whether an approver must provide a justification for their decision. Justification is visible to other approvers and the requestor.

Number of days before the request is forwarded to alternative approvers.

A block specifying the users who will be asked to approve requests, as documented below.

Maximum number of days within which a request must be approved. If a request is not approved within this time period after it is made, it will be automatically rejected.

Whether alternative approvers are enabled.

A block specifying alternative approvers when escalation is enabled and the primary approvers do not respond before the escalation time, as documented below.

Whether an approver must provide a justification for their decision. Justification is visible to other approvers and the requestor.

Number of days before the request is forwarded to alternative approvers.

A block specifying the users who will be asked to approve requests, as documented below.

Maximum number of days within which a request must be approved. If a request is not approved within this time period after it is made, it will be automatically rejected.

Whether alternative approvers are enabled.

A block specifying alternative approvers when escalation is enabled and the primary approvers do not respond before the escalation time, as documented below.

Whether an approver must provide a justification for their decision. Justification is visible to other approvers and the requestor.

Number of days before the request is forwarded to alternative approvers.

A block specifying the users who will be asked to approve requests, as documented below.

Maximum number of days within which a request must be approved. If a request is not approved within this time period after it is made, it will be automatically rejected.

Whether alternative approvers are enabled.

A block specifying alternative approvers when escalation is enabled and the primary approvers do not respond before the escalation time, as documented below.

Whether an approver must provide a justification for their decision. Justification is visible to other approvers and the requestor.

Number of days before the request is forwarded to alternative approvers.

A block specifying the users who will be asked to approve requests, as documented below.

Maximum number of days within which a request must be approved. If a request is not approved within this time period after it is made, it will be automatically rejected.

Whether alternative approvers are enabled.

A block specifying alternative approvers when escalation is enabled and the primary approvers do not respond before the escalation time, as documented below.

Whether an approver must provide a justification for their decision. Justification is visible to other approvers and the requestor.

Number of days before the request is forwarded to alternative approvers.

A block specifying the users who will be asked to approve requests, as documented below.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Whether to show the reviewer decision helpers. If enabled, system recommendations based on users' access information will be shown to the reviewers. The reviewer will be recommended to approve the review if the user has signed-in at least once during the last 30 days. The reviewer will be recommended to deny the review if the user has not signed-in during the last 30 days.

Specifies the actions the system takes if reviewers don't respond in time. Valid values are keepAccess, removeAccess, or acceptAccessRecommendation.

Whether a reviewer needs to provide a justification for their decision. Justification is visible to other reviewers and the requestor.

How many days each occurrence of the access review series will run.

Whether to enable assignment review.

This will determine how often the access review campaign runs, valid values are weekly, monthly, quarterly, halfyearly, or annual.

Self-review or specific reviewers. Valid values are Manager, Reviewers, or Self.

One or more reviewer blocks to specify the users who will be reviewers (when review_type is Reviewers), as documented below.

This is the date the access review campaign will start on, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z), default is now. Once an access review has been created, you cannot update its start date

Whether to show the reviewer decision helpers. If enabled, system recommendations based on users' access information will be shown to the reviewers. The reviewer will be recommended to approve the review if the user has signed-in at least once during the last 30 days. The reviewer will be recommended to deny the review if the user has not signed-in during the last 30 days.

Specifies the actions the system takes if reviewers don't respond in time. Valid values are keepAccess, removeAccess, or acceptAccessRecommendation.

Whether a reviewer needs to provide a justification for their decision. Justification is visible to other reviewers and the requestor.

How many days each occurrence of the access review series will run.

Whether to enable assignment review.

This will determine how often the access review campaign runs, valid values are weekly, monthly, quarterly, halfyearly, or annual.

Self-review or specific reviewers. Valid values are Manager, Reviewers, or Self.

One or more reviewer blocks to specify the users who will be reviewers (when review_type is Reviewers), as documented below.

This is the date the access review campaign will start on, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z), default is now. Once an access review has been created, you cannot update its start date

Whether to show the reviewer decision helpers. If enabled, system recommendations based on users' access information will be shown to the reviewers. The reviewer will be recommended to approve the review if the user has signed-in at least once during the last 30 days. The reviewer will be recommended to deny the review if the user has not signed-in during the last 30 days.

Specifies the actions the system takes if reviewers don't respond in time. Valid values are keepAccess, removeAccess, or acceptAccessRecommendation.

Whether a reviewer needs to provide a justification for their decision. Justification is visible to other reviewers and the requestor.

How many days each occurrence of the access review series will run.

Whether to enable assignment review.

This will determine how often the access review campaign runs, valid values are weekly, monthly, quarterly, halfyearly, or annual.

Self-review or specific reviewers. Valid values are Manager, Reviewers, or Self.

One or more reviewer blocks to specify the users who will be reviewers (when review_type is Reviewers), as documented below.

This is the date the access review campaign will start on, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z), default is now. Once an access review has been created, you cannot update its start date

Whether to show the reviewer decision helpers. If enabled, system recommendations based on users' access information will be shown to the reviewers. The reviewer will be recommended to approve the review if the user has signed-in at least once during the last 30 days. The reviewer will be recommended to deny the review if the user has not signed-in during the last 30 days.

Specifies the actions the system takes if reviewers don't respond in time. Valid values are keepAccess, removeAccess, or acceptAccessRecommendation.

Whether a reviewer needs to provide a justification for their decision. Justification is visible to other reviewers and the requestor.

How many days each occurrence of the access review series will run.

Whether to enable assignment review.

This will determine how often the access review campaign runs, valid values are weekly, monthly, quarterly, halfyearly, or annual.

Self-review or specific reviewers. Valid values are Manager, Reviewers, or Self.

One or more reviewer blocks to specify the users who will be reviewers (when review_type is Reviewers), as documented below.

This is the date the access review campaign will start on, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z), default is now. Once an access review has been created, you cannot update its start date

Whether to show the reviewer decision helpers. If enabled, system recommendations based on users' access information will be shown to the reviewers. The reviewer will be recommended to approve the review if the user has signed-in at least once during the last 30 days. The reviewer will be recommended to deny the review if the user has not signed-in during the last 30 days.

Specifies the actions the system takes if reviewers don't respond in time. Valid values are keepAccess, removeAccess, or acceptAccessRecommendation.

Whether a reviewer needs to provide a justification for their decision. Justification is visible to other reviewers and the requestor.

How many days each occurrence of the access review series will run.

Whether to enable assignment review.

This will determine how often the access review campaign runs, valid values are weekly, monthly, quarterly, halfyearly, or annual.

Self-review or specific reviewers. Valid values are Manager, Reviewers, or Self.

One or more reviewer blocks to specify the users who will be reviewers (when review_type is Reviewers), as documented below.

This is the date the access review campaign will start on, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z), default is now. Once an access review has been created, you cannot update its start date

Whether to show the reviewer decision helpers. If enabled, system recommendations based on users' access information will be shown to the reviewers. The reviewer will be recommended to approve the review if the user has signed-in at least once during the last 30 days. The reviewer will be recommended to deny the review if the user has not signed-in during the last 30 days.

Specifies the actions the system takes if reviewers don't respond in time. Valid values are keepAccess, removeAccess, or acceptAccessRecommendation.

Whether a reviewer needs to provide a justification for their decision. Justification is visible to other reviewers and the requestor.

How many days each occurrence of the access review series will run.

Whether to enable assignment review.

This will determine how often the access review campaign runs, valid values are weekly, monthly, quarterly, halfyearly, or annual.

Self-review or specific reviewers. Valid values are Manager, Reviewers, or Self.

One or more reviewer blocks to specify the users who will be reviewers (when review_type is Reviewers), as documented below.

This is the date the access review campaign will start on, formatted as an RFC3339 date string in UTC(e.g. 2018-01-01T01:02:03Z), default is now. Once an access review has been created, you cannot update its start date

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

A block describing the content of this question, as documented below.

One or more blocks configuring a choice to the question, as documented below.

Whether this question is required.

The sequence number of this question.

A block describing the content of this question, as documented below.

One or more blocks configuring a choice to the question, as documented below.

Whether this question is required.

The sequence number of this question.

A block describing the content of this question, as documented below.

One or more blocks configuring a choice to the question, as documented below.

Whether this question is required.

The sequence number of this question.

A block describing the content of this question, as documented below.

One or more blocks configuring a choice to the question, as documented below.

Whether this question is required.

The sequence number of this question.

A block describing the content of this question, as documented below.

One or more blocks configuring a choice to the question, as documented below.

Whether this question is required.

The sequence number of this question.

A block describing the content of this question, as documented below.

One or more blocks configuring a choice to the question, as documented below.

Whether this question is required.

The sequence number of this question.

The actual value of this choice.

A block describing the display text of this choice, as documented below.

The actual value of this choice.

A block describing the display text of this choice, as documented below.

The actual value of this choice.

A block describing the display text of this choice, as documented below.

The actual value of this choice.

A block describing the display text of this choice, as documented below.

The actual value of this choice.

A block describing the display text of this choice, as documented below.

The actual value of this choice.

A block describing the display text of this choice, as documented below.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The localized content of this question.

The ISO 639 language code for this question content.

The localized content of this question.

The ISO 639 language code for this question content.

The localized content of this question.

The ISO 639 language code for this question content.

The localized content of this question.

The ISO 639 language code for this question content.

The localized content of this question.

The ISO 639 language code for this question content.

The localized content of this question.

The ISO 639 language code for this question content.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The default text of this question.

One or more blocks describing localized text of this question, as documented below.

The localized content of this question.

The ISO 639 language code for this question content.

The localized content of this question.

The ISO 639 language code for this question content.

The localized content of this question.

The ISO 639 language code for this question content.

The localized content of this question.

The ISO 639 language code for this question content.

The localized content of this question.

The ISO 639 language code for this question content.

The localized content of this question.

The ISO 639 language code for this question content.

A block specifying the users who are allowed to request on this policy, as documented below.

Whether to accept requests using this policy. When false, no new requests can be made using this policy.

Specifies the scopes of the requestors. Valid values are AllConfiguredConnectedOrganizationSubjects, AllExistingConnectedOrganizationSubjects, AllExistingDirectoryMemberUsers, AllExistingDirectorySubjects, AllExternalSubjects, NoSubjects, SpecificConnectedOrganizationSubjects, or SpecificDirectorySubjects.

A block specifying the users who are allowed to request on this policy, as documented below.

Whether to accept requests using this policy. When false, no new requests can be made using this policy.

Specifies the scopes of the requestors. Valid values are AllConfiguredConnectedOrganizationSubjects, AllExistingConnectedOrganizationSubjects, AllExistingDirectoryMemberUsers, AllExistingDirectorySubjects, AllExternalSubjects, NoSubjects, SpecificConnectedOrganizationSubjects, or SpecificDirectorySubjects.

A block specifying the users who are allowed to request on this policy, as documented below.

Whether to accept requests using this policy. When false, no new requests can be made using this policy.

Specifies the scopes of the requestors. Valid values are AllConfiguredConnectedOrganizationSubjects, AllExistingConnectedOrganizationSubjects, AllExistingDirectoryMemberUsers, AllExistingDirectorySubjects, AllExternalSubjects, NoSubjects, SpecificConnectedOrganizationSubjects, or SpecificDirectorySubjects.

A block specifying the users who are allowed to request on this policy, as documented below.

Whether to accept requests using this policy. When false, no new requests can be made using this policy.

Specifies the scopes of the requestors. Valid values are AllConfiguredConnectedOrganizationSubjects, AllExistingConnectedOrganizationSubjects, AllExistingDirectoryMemberUsers, AllExistingDirectorySubjects, AllExternalSubjects, NoSubjects, SpecificConnectedOrganizationSubjects, or SpecificDirectorySubjects.

A block specifying the users who are allowed to request on this policy, as documented below.

Whether to accept requests using this policy. When false, no new requests can be made using this policy.

Specifies the scopes of the requestors. Valid values are AllConfiguredConnectedOrganizationSubjects, AllExistingConnectedOrganizationSubjects, AllExistingDirectoryMemberUsers, AllExistingDirectorySubjects, AllExternalSubjects, NoSubjects, SpecificConnectedOrganizationSubjects, or SpecificDirectorySubjects.

A block specifying the users who are allowed to request on this policy, as documented below.

Whether to accept requests using this policy. When false, no new requests can be made using this policy.

Specifies the scopes of the requestors. Valid values are AllConfiguredConnectedOrganizationSubjects, AllExistingConnectedOrganizationSubjects, AllExistingDirectoryMemberUsers, AllExistingDirectorySubjects, AllExternalSubjects, NoSubjects, SpecificConnectedOrganizationSubjects, or SpecificDirectorySubjects.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.

Specifies the type of users. Valid values are singleUser, groupMembers, connectedOrganizationMembers, requestorManager, internalSponsors, or externalSponsors.

For a user in an approval stage, this property indicates whether the user is a backup fallback approver.

The ID of the subject.