Understanding Organizations, Projects, and Roles
ScreenKey is organized around three core elements: Organizations, Projects and User Roles.
A simple way to understand how they work together:
- Organizations create and own Projects.
- Projects contain media and workflows.
- Users receive access based on what they need to do within an Organization or Project.
- One User may have different Roles across different Organizations and Projects.
Organization Access vs. Project Access
It is important to distinguish between Organization-level and Project-level access.
- Organization-level access is granted to Owners and Team Members. It provides access across the Organization and its Projects, depending on the Team Member’s permissions.
- Project-level access is limited to a specific Project or workflow. Reviewers, Uploaders and Approvers only receive the access required for the task they were invited to complete.
Having access to a Project does not make someone a Team Member of the Organization.
Organizations
An Organization is the administrative account that owns and manages Projects. It contains the Organization Owner and any invited Team Members.
A new User becomes the Owner of an Organization when they create their first Project. Users can also become Team Members when invited to join an existing Organization.
Organizations can:
- Create, own and manage Projects
- Invite and manage Team Members
- Control permissions and security settings
- Manage workflows, billing and account-level settings
A User may belong to one or multiple Organizations, with different permissions in each.
Important: Projects belong to Organizations—not to individual Users. If you cannot find a Project you manage, confirm that you are working in the correct Organization.
Projects
A Project is a workflow containing media files, folders or Galleries. Each Project has its own settings for uploading, sharing, reviewing and downloading content.
A Project can represent anything from a single screener to an entire season or production workflow. Its structure depends on the content, audience and intended use.
For example:
- A finished feature film may use one Project containing a sales screener.
- A television series in post-production may use multiple Projects organized by episode, department or workflow.
- A marketing campaign may use a Project to organize and distribute publicity assets.
Projects can be presented in two modes:
- Theater Mode: Best for polished presentations, screeners and external review.
- Workspace Mode: Best for work-in-progress media and active collaboration.
Depending on their Role, a User may be able to upload or access media, provide feedback, view analytics, download content or manage sharing and security settings.
User Roles
ScreenKey Roles are based on a User’s access and permissions—not their real-world job title.
The four primary Roles are:
Team Members
Team Members help administer an Organization. Depending on the permissions assigned by the Organization Owner, they may be able to:
- Create and manage Projects
- Upload and organize media
- Invite Users and manage access
- Configure Project settings
- View analytics
- Manage Organization or billing settings
Reviewers
Reviewers securely watch content shared with them. Depending on the permissions granted, they may also be able to:
- Provide feedback or comments
- Mark a review complete
- Download media
Reviewer access applies only to the Projects and content shared with them.
Uploaders
Uploaders upload media to a Project after being invited with Upload Access.
Uploaders access does not automatically include permission to watch or review other Project media. If a Uploader also needs to review content, they must be granted separate Reviewer access.
Approvers
Approvers review media assigned to them through a Media Approval workflow. They may be able to:
- Approve or reject media
- Mark favourites
- Download assigned content
- Submit final approval decisions
Key Takeaway
A User’s Role determines what they can do, while their Organization or Project access determines where they can do it.
When granting access, provide only the permissions the User needs to complete their intended task.