Managing access with Oropod Storage

If you use Oropod Storage for a project, you can use multiple workspaces to give different team members different levels of access. Each person will only see files from the workspaces they have access to, and metadata-based navigation (day, scene, shot, tag etc.) works automatically and transparently across the workspaces. Within a workspace, we can also set whether each person can download files or only view them.

This page walks through a typical setup for a DIT who will upload files to both workspaces. The example project has two workspaces:

  • Dailies, which everyone on the project can see
  • Dailies (sensitive), which only a smaller group of people have access to

Setting it up

Workspaces are not self-service yet, so email us at info@oropod.com with the project and the people who should see the sensitive workspace. We create the workspace, give those people access and send you its upload credentials. You can add or remove people later the same way, and the list can start short, e.g. just the producer and the DIT.

Uploading as the DIT

  • Each workspace has its own SFTP username and password, both on sftp.oropod.com, port 2022 (see Uploading to Oropod Storage).
  • Save each login as its own bookmark in your file transfer app, and name them so you can’t mistake one for the other, e.g. Dailies and Dailies – SENSITIVE.
  • Check which bookmark you’re connected to before you start an upload. Whatever you upload with the regular login is visible to everyone on the project.
  • Upload sensitive clips with the sensitive login only, in the same folder structure you use for the rest.

If you uploaded a sensitive clip with the regular login by mistake, delete it there right away, upload it again with the sensitive login, and let us know.

What the rest of the team sees

People with access to the sensitive workspace don’t need to do anything. Within a couple of minutes it appears as an extra source under Sources, and its clips appear under the same days, scenes and shots as everything else.

Everyone else sees no trace of the sensitive clips in days, scenes or shots, and doesn’t see the sensitive workspace under Sources.

Where to put report files

Oropod reads report files, such as Silverstack XML or a take report, from each workspace a viewer can see, and applies them to clips in any of those workspaces (see Importing metadata). A report in Dailies can therefore describe sensitive clips too, and people with sensitive access see the sensitive clips with the metadata applied.

Which workspace a report belongs in depends on what it says:

  • If only the footage is sensitive, keep your usual reports in Dailies. One report per day can cover both workspaces’ clips, and everyone gets the metadata they’re allowed to see.
  • If the report’s contents are sensitive too, e.g. scene descriptions, notes or tags, export the sensitive clips’ report separately and upload it with the sensitive login, and leave those clips out of the report in Dailies. People with sensitive access can still see both workspaces, so nothing is lost for them.

Anyone with access to a workspace can read every file in it, report files included, even though the app doesn’t show their contents. Treat a report in Dailies as readable by the whole team.

Tips

  • Clips and reports don’t need to arrive together. A report can go up before or after the clips it describes, in either workspace.
  • To check an upload landed in the right place, open the project in Oropod and look under Sources, where each workspace is listed by name.