This Getting Started series begins with planning and preparation. Having a comprehensive plan before configuring your workspace sets the foundation to save time and clarify workflows when you start project work.
We know you're probably eager to get going, dive into a project, and make exciting things happen - time is of the essence! Since this is a self-paced series of articles, you are always welcome to go through as you'd like; however, we recommend following the series as laid out for the most effortless setup.
Depending on your project(s) complexity and team size, the points in this planning section may require more or less time and consideration.
Who should complete this guide?
The person who created the ftrack workspace will be the first "Administrator" with open permission to make the necessary updates. Typically, this person completes ftrack's initial configuration as laid out in this guide.
If that is not the case, they will need to assign the designated user an "Administrator" role in ftrack.
Need help determining who this should be? Review the "System Administrator" function under Establish your Workspace Team.
|
Create a new Account and assign an Administrator Role:
|
Establish your Workspace Team
When onboarding your company to ftrack, we recommend setting up a team responsible for implementing and maintaining the workspace. This is your "Steering Committee."
If you're working at a smaller company, a single person may steer all decisions.
The larger your team and projects are, the more critical these roles are, as your workspace will likely have additional moving parts to consider. This committee can ensure that your workspace is conducive to the greater team and communicate important workflow updates.
Here are some suggested functions for your launch team:
-
System Administrator – the person responsible for the ftrack Account, as well as overseeing and driving ftrack's implementation within the company and coordinating other resources. Often, a senior member of the project management or operations team.
- An Administrator (Admin) role in ftrack has full accessibility to system settings, meaning they can make changes to the product that affect how all projects and workflows are structured. It is optimal to keep this role designated to one person so they can systematically control and communicate the flow of change to the workspace.
- Exception: If you have a large team with offices in multiple locations/time zones, you may wish to have an Admin in each location to make crucial changes when needed. However, if you go this route, we recommend creating a system of communication and agreement, so all Admins know about any workspace requests or emergency updates.
- Workflow Specialist(s) – an individual who understands the company's workflow/creative process and can help to define this within the ftrack workspace. You may include a few people who collaborate and agree on a singular way forward and work with the System Administrator who makes the changes to the workspace.
- Application and Integrations Expert – an individual with knowledge of the applications, e.g., Adobe products, Maya, Nuke, or other pipeline applications, that you use in production at your company. This is for those who will be using Connect & Integrations.
- (Optional) Technical Guru – a technical resource if you plan to build automation, customize ftrack, or develop integrations. This is for those leveraging Integrations, Actions, or the API.
Take Action
 |
Take a moment to think about your team and select the person best suited to each function and responsibility. Remember that this may be one person if you have a smaller team, as you may not utilize each function. |
Next, we guide you through establishing project goals, which translates to how you will use ftrack Studio.