Skip to main content

Projects

Projects Overview​

Projects are used to restrict access to resources.

To view projects navigate to tab in the section in the top right panel.

  • Click on the project name to open the project overlay.

  • Optionally, click on the Three dots and then click Open overlay option.

  • View the following sections in the left panel.

    • . Members: the viewable members within the project.
    • . Subprojects: the viewable subprojects of the selected project.
    • . Security Requirements: your active security requirements for the project.

  • Click Exit button in the top left corner.

note
  • If you cannot view everything in the video above in your front-end, it means you do not have permissions to carry out the actions above.
  • With the correct permissions, you can be added or removed from a project.
  • Understanding the role of the project in tiCrypt will allow you to make full use of the system potential.
View Projects
note

If you cannot view all sections within a project, then you do not have the viewing permissions from your admin.

info

Projects, sub-projects, security levels and security requirements are only created by admins.

Project Hierarchy Tree​

Tree

The root project in the system is the "Unlocked" system. Any project created in the system is some descendant of the root. The root is called "Unlocked" because it is a project with NO requirements.

When a new project gets created, the parent of that project is "unlocked". From a project, a user can create as many subprojects as they would like. These subprojects have the same security levels of the parent project.

Essentially, if there is a VM tagged by AA, then only a drive of either AA, A, or ''Unlocked'' can be used in this drive. The same applies for transferring files into a VM. If a file is tagged by project BB, then it can go into a VM of BB, BBA, BBB, or BBC. A file tagged by BB CANNOT go into a VM tagged by AB, B, or "Unlocked".

note

Once a resource goes into a VM, it takes on that project as its own project. If there was a file tagged by A and it was transferred into ABA, if the file was to be removed it's project would be ABA.

info

The following actions can be only performed with custom permissions from your admin.​

Create Project via Vault​

To create a new project navigate to the tab in the section on the right.

  • Click the button in the top right.
  • In the prompt, type a tag name and select a tag preferred color.
  • Type the project name.
  • Optionally, type a project description.
  • Optionally, select a security level for the project.
  • Optionally, type the name of the principal investigator (PI).
  • Click .
Create Project via Vault

Add User(s) to Project via Vault​

To add members to a project navigate to the tab in the section on the right.

  • Select the appropriate project.
  • Click the Three dots button in the right.
  • Click on the Add member(s) option.
  • In the prompt, type in the user name(s),
  • Optionally, type a membership expiration date.
  • Select the role of user(s) in the project.
  • Select user project restrictions.
  • Select whether users` expiration date will be skipped or attempted to be renewed.
  • Click .
Create a sub-project from the Vault
note

A user can add members to a project if they have the correct permissions to do so.

caution

A user may be added to a project but if the user does not have all of the certifications from each security requirement that make up that project then they will not be able to view resources tagged by that project.

Create subproject via Vault​

To create a subproject navigate to the tab in the section on the right.

  • Select the project you would like to create a subproject of.
  • Click the Three dots button in the right.
  • Click the Create subproject option.
  • In the prompt, type a tag name and select a tag preferred color.
  • Type the subproject name.
  • Optionally, type a subproject description.
  • Optionally, select a security level for the subproject.
  • Optionally, type the name of the principal investigator (PI).
  • Click .
note

Newly created projects are available upon re-login.

Create a sub-project from the Vault

Assign Project to Subadmin via Vault​

To assign a project to a subadmin navigate to the tab in the section on the right.

  • Select the project you would like to assign to a sub-admin.
  • Click the Three dots button in the right.
  • Click on the Assign project to Sub-admin(s) button in the top right.
  • In the prompt, type the name of the sub-admin(s) you want to assign the project to.
  • Click .
Assign Project to Subadmin via Vault

Edit project membership via Vault​

To edit a project membership navigate to the tab in the section on the right.

  • Select the project you would like to edit.
  • Click the Three dots button in the right.
  • Click the Edit option.
  • In the prompt, edit tag text and color, name and project description, security level or the principal investigator.
  • Once you finished, click .
Edit Project via Vault

Make an announcement via Vault​

To make an announcement navigate to the tab in the section on the right.

  • Select the project where you want to make an announcement.
  • Click the Three dots button in the right.
  • Click the Make an announcement option.
  • In the prompt, type your announcement.
  • Click .
Make an Announcement via Vault

Delete Project via Projects​

To delete a project navigate to the tab in the section on the right.

  • Select the project you would like to delete.
  • Click the Three dots button in the right.
  • Click the Delete option.
  • In the prompt, click .
caution

To be able to delete a project, you must remove all its members (including yourself).

Delete Project via Vault
The **root project** in the system is the **`Unlocked`** because it is a **project** with **no requirements**.

  • All projects created in the system are descendants of the root.

  • For every newly created project, the parent is Unlocked.

  • You can create an unlimited number of subprojects from a single project.

  • Created subprojects have the same security levels of the parent project.

If a VM tagged by , then only a drive of either , , or Unlocked can be used in this drive.

The same applies to transferring files into a VM.

If a file is tagged by project , then it can go into a VM of , ,, or .

A file tagged by CAN NOT go into a VM tagged by , , or Unlocked.

note

You may also inherit project open overlay permissions from your admin which will allow you to create, edit or delete project memberships, subprojects, security requirements and member certifications. Once a resource goes into a VM, it takes on that project as its own project. If there was a file tagged by and it was transferred into , if the file was to be removed its project would be .