Projects and Users¶
Projects¶
Use New Project to choose a location and define a name, code, and optional notes. Flowinator creates the pipeline folders automatically and remembers recently opened projects on the local workstation.
Use Select Project to open an existing Flowinator project. A valid project contains 00_Pipeline/Metadata/project.json.
Project Settings lets a Project Admin update the project name and notes, review its location, enable episode mode, and manage users.
Video: Create a project¶
Choose a location, define the project name and permanent project code, then let Flowinator create the required folders.
Video: Change the project name¶
A Project Admin can rename the project later in Project Settings. The project code is intentionally permanent because it is used as the project folder identity.
Video: Open a previous project¶
Select Project includes a Recent Projects list, making previously opened projects on the same workstation easy to find and reopen.
Users¶
Users are local project records stored in 00_Pipeline/Metadata/users.json. They are not cloud accounts. The active login is stored separately on each workstation, so opening the same shared project does not automatically log another user in.
| Role | Permissions |
|---|---|
| Project Admin | Manage project settings, users, roles, and all project items. |
| Artist | Read and create production work; delete only items they own. |
The first user of a project becomes a Project Admin. A project must always keep at least one Project Admin.
Video: Create users and assign roles¶
Use Project Settings to add users and choose the appropriate Project Admin or Artist role.
Example¶
- The admin creates
MIRNAVand adds artists. - An artist logs in before creating a workfile.
- New versions record the logged-in username, date, version number, and optional commit.
- The admin can review users and change roles from Project Settings.