# Programs

Violet <mark style="color:purple;">**Programs**</mark> contain data like Requirements, Schedules and Systems. They can be used to enable granular permissions to Requirements and other features.

## Create a program

Any user can create a program; begin by navigating to **Tools** → **Programs** and click **+Program**:

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FG1ziqqUkYJpF9EdVTrNf%2Fcreate%20new%20programs%20button.png?alt=media&#x26;token=108c74a9-572b-4c5f-8bc4-2a9a4536266d" alt="" width="563"><figcaption></figcaption></figure>

Alternatively, new programs can be created directly from the Violet Requirements page. In the dropdown menu at the top of the screen, select **Create New:**

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FBChB3vZPPtRJEG92qoaa%2Fcreate%20new%20program%20from%20requirements.png?alt=media&#x26;token=2188f65f-b24f-4960-b51f-aefe1d265151" alt="" width="470"><figcaption></figcaption></figure>

In the **New Program** window, enter a program Name and Description (optional).

## Assign team members

Assign one or more users as **Program Managers**, which grants them administrator-level permissions to manage the program, as well as edit access to any requirements within the program.&#x20;

Next, assign users or groups as **Team Members.** Team members have **read** access to the program. They will be able to view all details about the program as well as all requirements within the program. The "All Users" group consists of all users internal to your organization's Violet instance.&#x20;

See [invite-your-team](https://docs.violetlabs.com/resources/administrative/invite-your-team "mention") for guidance on setting up user groups.

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FxJvxvN06Iv3kpHSh7OMs%2Fenter%20program%20name%20and%20description.png?alt=media&#x26;token=d1426c7c-a635-4e07-b3b3-ad94124efc7a" alt="" width="563"><figcaption></figcaption></figure>

### Adding guest users

We want to make it easy to collaborate with external users while maintaining control of your data.

To invite external or "guest" users, e recommend creating a dedicated user group for any external Violet users who require read-access to the program, then add that external group as a team member for the appropriate program(s). These guest users can review Violet requirements and add comments, but can't see other Violet platform data.

## Create System Elements and Custom Requirement Fields

Finally, you can define [systems](https://docs.violetlabs.com/features/requirements/systems "mention")  and [custom-fields](https://docs.violetlabs.com/features/requirements/custom-fields "mention") for the requirements in a program.

Assigning users or groups to System elements grants them **edit** access to the requirements within that system; these users are the designated requirement **owners**.&#x20;

Systems can also be used to filter, sort, visualize and track progress of Violet Requirements - read more [here](https://docs.violetlabs.com/features/requirements/systems).

## Hide Inactive Programs

Toggle the **Active** button to mark a program as **inactive.** This feature hides the program from the requirements drop down list.

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2FuVyYoU2QRCIwuuYbOfgJ%2Fimage.png?alt=media&#x26;token=ae7abbaf-9d41-41f2-9128-44630cd301a3" alt=""><figcaption></figcaption></figure>

If you still wish to view requirements from an inactive program, use the **Show Inactive Programs** toggle in the requirements pulldown menu.

<figure><img src="https://2091741164-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvrraExym8pNEUvBDoima%2Fuploads%2F34hBwmUiRLCnu44X3S0E%2Fimage.png?alt=media&#x26;token=f03b18c8-4fe9-4b04-ab04-385375c4a83a" alt=""><figcaption></figcaption></figure>
