# Time-bound access

Time-bound access limits an application permission to a defined date window. Use it when a member needs access for a production, rehearsal period, temporary assignment, or other limited engagement.

The access window is part of an environment permission. It works with the selected application role and studios; it does not replace either one.

## When No Dates Are Specified

If both the start and end dates are left blank, the permission is available immediately and does not expire automatically. The member keeps access until an Owner or Admin edits or deletes the permission, removes the member from the organization, or the assigned application, studio, or environment is no longer available.

The permission remains limited to its assigned application role and studios. Leaving the dates blank does not grant broader access.

## Before You Begin

Confirm that:

- the user has joined the organization as a Member;
- the required application is enabled in the correct environment;
- the production resources are assigned to the appropriate studios;
- you know which [application role](/manage-organization/roles-and-permissions/#application-roles) the member needs; and
- the planned window includes setup, rehearsal, the production, expected overrun, and recovery work.

:::caution
Do not set the window to the scheduled program time alone. A tight window can block access during setup or while the crew is handling an overrun or production issue.
:::

## Add Time-Bound Access

1. Open **Environment Settings** in the correct environment.
2. Under **User Permissions**, select **Add Permission**.
3. Select the member and application.
4. Select the application role required for the assignment.
5. Select one or more studios containing the resources the member needs.
6. Set the start and end dates for the access window.
7. Save the permission.

Create a separate permission record for each additional application the member needs.

## Choose a Safe Access Window

Include time for:

- configuration and preproduction checks;
- rehearsals and operator handoff;
- the scheduled production;
- a reasonable overrun; and
- troubleshooting, recovery, and shutdown verification.

For recurring work, review whether one longer window or separate permission records better matches the production schedule. Avoid leaving temporary access open indefinitely.

## Verify Access

Before the production:

1. Confirm the permission lists the intended member, application role, studios, and dates.
2. Ask the member to select the correct organization and environment.
3. Confirm that the assigned application and resources are available during the access window.
4. Confirm that resources outside the assigned studios are not available to the member.

## Change or Remove Access

Edit the permission when the production schedule, role, or studio assignment changes. Delete the permission when the member no longer needs access.

Removing an application permission does not remove the person from the organization. To revoke organization membership, use **Organization Settings** and remove the member.