Sign in
role_user_assignments

Use this endpoint to give a user permission to a resource or an organization. The needed data is the user, the role definition, and the object id. The object must be of the type specified in the role definition. The type given in the role definition and the provided object_id are used to look up the resource.

After creation, the assignment cannot be edited, but can be deleted to remove those permissions.

get/role_user_assignments/{id}/

Path parameters

idinteger required

A unique integer value identifying this role user assignment.

Response

idinteger required
urlstring required
relatedobject required
summary_fieldsobject required
createdstring date-time required

The date/time this resource was created

created_byinteger nullable required

The user who created this resource

content_type'eda.activation' | 'eda.auditrule' | 'eda.decisionenvironment' | 'eda.edacredential' | 'eda.eventstream' | 'eda.project' | 'eda.rulebook' | 'eda.rulebookprocess' | 'shared.organization' | 'shared.team' required
  • eda.activation - Activation
  • eda.auditrule - Audit Rule
  • eda.decisionenvironment - Decision Environment
  • eda.edacredential - Eda Credential
  • eda.eventstream - Event Stream
  • eda.project - Project
  • eda.rulebook - Rulebook
  • eda.rulebookprocess - Rulebook Process
  • shared.organization - Organization
  • shared.team - Team
object_idstring nullable

Primary key of the object this assignment applies to, null value indicates system-wide assignment

object_ansible_idstring uuid nullable

Resource id of the object this role applies to. Alternative to the object_id field.

role_definitioninteger required

The role definition which defines permissions conveyed by this assignment

userinteger
user_ansible_idstring uuid nullable

Resource id of the user who will receive permissions from this assignment. Alternative to user field.

Changes

Changed in 4 of the 8 revisions of this API.313

  • c04fc5f09692211See the full diff
    • ▲

      the response property object_ansible_id became nullable for the status 200

      response-property-became-nullable

    • ▲

      the response property user_ansible_id became nullable for the status 200

      response-property-became-nullable

    • ●

      added the new eda.eventstream enum value to the content_type/allOf[ContentTypeEnum]/ response property for the response status 200

      response-property-enum-value-added

    • ○

      removed the eda.credentialtype enum value from the content_type/allOf[ContentTypeEnum]/ response property for the response status 200

      response-property-enum-value-removed

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • feeac1db5ade1See the full diff
    • ○

      removed the eda.extravar enum value from the content_type/allOf[ContentTypeEnum]/ response property for the response status 200

      response-property-enum-value-removed

    This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • cbf68ddd97601See the full diff
    • ○

      endpoint added

      endpoint-added

    This revision also has 24 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 62d33b7908341See the full diff
    • ▲

      api path removed without deprecation

      api-path-removed-without-deprecation

    This revision also has 64 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog