Access Rights Attribution

An access right links a profile to an access policy for a validity period. It is required for a profile to book, to have reservations made on its behalf, or to enter. For the profile lifecycle itself, see Profile Provisioning.

Three ways to grant rights

Method	Who decides	How
Default rights	Administrator	Assigned automatically to every new profile, according to the organization settings
Tag-based rights	Administrator configures, your system tags	Access policies are linked to tags. Setting or removing a tag on the profile (at creation or with `PATCH /profiles`) adds or removes the rights
Explicit rights via API	Your system	`POST`, `PATCH` and `DELETE` on `/access-rights`

Tag-based rights are maintained by Izix: a tag change adds or removes the linked rights. Our recommendation is to use one method per access policy, so that a tag update and an explicit API call never compete for the same right.

Explicit attribution

sequenceDiagram
    autonumber
    participant P as Your system
    participant API as Izix Public API
    P->>API: GET /access-policies
    API-->>P: Policies (id, type, parking lot, validity)
    P->>API: POST /access-rights (profile, access_policy_id, valid_from, valid_to)
    API-->>P: access_right_id
    P->>API: PATCH /access-rights/{accessRightId} (new valid_to)
    API-->>P: access_right_id
    P->>API: DELETE /access-rights/{accessRightId}
    API-->>P: 204 (400 if the right is already closed)

Field	Description
`profile_external_reference` or `profile_id`	The profile
`access_policy_id`	From `GET /access-policies`
`valid_from`, `valid_to`	Validity of the right. `valid_to` is optional
`planning_period`	Number of days the profile can book in advance
`budget_policy_id`	Budget paying for the usage, when the policy is paid
`send_notification`	Email the profile about the change. Default is no email

To read the rights of profiles: GET /access-rights with filters[profile_external_references][] or filters[profile_ids][].

Usage notes

Default rights suit simple cases where every employee gets the same access.
Tags give precise control without your system knowing access policy IDs. Keep tags up to date when a user changes role or department.
Configuration matters: a wrong tag or policy configuration grants wrong permissions. Validate the setup with the organization administrator before going live.