Projects
Projects Overview
tiCrypt protects user data through end-to-end encryption, ensuring that even if an attacker gains access to the servers, they will only be able to access encrypted data without the decryption keys, which are not stored on the server.
While relying solely on cryptographic functions for security measures is not feasible due to performance and user convenience, projects serve as a conventional protection system based on administrator-defined access controls in conjunction with the end-to-end encryption.
The core of tiCrypt are its projects; which allow for resource tagging and determine access privileges. Tagging a resource, such as a file or group, with a project restricts access to specified users. Projects consist of a security level, name, description, and set of members. Projects can also have subprojects
, forming a hierarchy
.
- Projects serve as a security tagging mechanism.
- Projects enable any type of resource to be protected and shared only with members of that project.
- Once a resource is tagged with a project label, its accessibility and manipulation are significantly restricted.
- Projects are composed of
security levels
, which consist of one or moresecurity requirements
.
You cannot create a project without a security level. This is because a project is a group of requirements that makes up a security level.
A user can view when the project was created when it was last modified, the security level that it tags, and the Principal Investigator. The security requirements that make up the security level are also displayed.
The Projects
section, is the place where you can:
- . Add new members to project
- . Open project overlay
- . Make an anouncement to all project members
- . Edit the project details
- . Create sub-project from the selected project
- . Assign the project to a sub-admin
- . Delete the project
Projects Open Overlay
Project Role Permissions
- User roles can only reach projects from their
profile
or theproject
section in tab. - Admin roles can reach projects from the tab and have different workflows.
Projects can be tagged in the tab in the Drives
section. Attaching the project-tagged drive
to a VM will make the project VM tagged
.
View Projects Workflows
To view the projects, navigate to the tab. From this point, you have three common workflows to access projects.
Workflow via Management Projects:
- Navigate to
Projects
section. - Search the project you would like to view.
- Select the project.
- Click the
Open Overlay
button in the top right. - In the prompt, view the project options.
- Click
Exit
in the top left.
Workflow via Management Users:
- Navigate to
Users
section. - Select the user you would like to view the project of.
- Click the
Open Overlay
button in the top right. - In the prompt, select the
Projects
card on the left. - View the existing projects for the selected user.
- Click
Exit
in the top left.
Workflow via Vault Projects:
- In the tab, navigate to section.
- Select the project you would like to view.
- Click the
Three dots
button on the right. - Click the
Open Overlay
button in the top right. - In the prompt, view the project options.
- Click
Exit
in the top left.
Performing a change project
(tagging an element to a project) action anywhere in tiCrypt requires you to be part of that project.
You can Add member(s)
to project(s) and Assign
projects to Subadmin(s)
in bulk by selecting multiple projects.
The Open Overlay
is a workflow option that can be accessed from most tab sections.
Use the Open Overlay
to access the following:
The Members
card, where you can:
*. Add users to project
- . Edit existing members
- . Remove existing members
The Subprojects
card, where you can:
- . Create a new subproject
- . Edit existing subprojects
- . Delete existing subprojects
- . Assign subprojects to sub-admins
- . Create a sub-project to the selected sub-subproject
- . Make an announcement to all sub-project members
- . Add new members to the sub-project
The Security Requirements
card, where you can:
- . Edit security level
- . Certify users for a security requirement
- . Edit existing security requirements
- . Delete existing security requirements
The Member Certifications
card, where you can:
- . Certify users for a security requirement
- . Delete certifications from specified users
- . Mark certifications as expired
- . Edit/Renew certifications
Create a new Project via Projects
To create a new project navigate to the tab in the Projects
section.
- 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 .
A project may only have one security level assigned to it.
Add member(s) to Project via Projects
To add new member(s) to project navigate to the tab in the Projects
section.
- Select the project you would like to add member(s) to.
- Click the
Add member(s)
button in the top right. - In the prompt, type the name of the user(s) you want to add to the project.
- Optionally, type a membership expiration date.
- Select the role in the project.
- Select the project restrictions.
- Select whether you would like to skip memberships or attempt their update.
- Click .
Create Subproject via Projects
- A subproject is a project that is branched off of a parent.
- Subprojects do not inherit any access restrictions from the parent.
- A user might be able to access resources tagged with a particular project, but not be able to access resources tagged with a parent project.
To create a subproject navigate to the tab in the Projects
section.
- Select the project you would like to create a subproject of.
- Click the
Create subproject
button in the top right. - 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 .
Subprojects can have different security levels from their parent project and are independent in terms of access control. However, the project hierarchy determines which resources can be tagged with a specific project.
Adding users to a sub-project will automatically adds them to the parent project.
Before you can add a user to a subproject / make them a member, they must be a member of any ancestor projects (parent, parent's parent, etc.). To maintain this relationship, you also cannot remove a user from a project until you have removed them from any descendant projects.
Assign project(s) to Subadmin(s) via Projects
To assign a project to a subadmin navigate to the tab in the Projects
section.
- Select the project you would like to assign to a sub-admin.
- 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 on .
Edit Project via Projects
To edit a project navigate to the tab in the Projects
section.
- Select the project you would like to edit.
- Click on the
Edit
button in the top right. - In the prompt, edit tag text and color, name and project description, security level or the principal investigator.
- Once you finished, click .
Projects can be edited either in the or in the tab.
Make an Announcement in Project via Projects
To make an announcement navigate to the tab in the in the Projects
section.
- Select the project where you want to make an announcement.
- Click on the
Make an announcement
button in the top right. - In the prompt, type your announcement.
- Click .
- A user can
make an announcement
of up to 250 characters to all users that have memberships to the project. - The announcement will appear in notifications which can be accessed by clicking on the
Notifications
button in the top right corner.
Notifications older than three months will be automatically archived by default. You may change this setting on request.
No matter your admin role, you must be a member of the project to be able to make announcements to its members.
Delete Project via Projects
To delete a project navigate to the tab in the Projects
section.
- Select the project you would like to delete.
- Click on the
Delete
button in the top right. - Click .
A user can delete a project if there are no subprojects nested underneath that project and the project does not have any members.
You will not be able to delete a project even if you are the only member of it. All projects may only be deleted from the tab by an admin.
Do not delete security requirements when deleting a project because security requirements may be still in use by other projects.