For the complete documentation index, see llms.txt. This page is also available as Markdown.

Roll out Shade company-wide

An admin's checklist for rolling Shade out to a large organization, with SSO, SCIM, managed installs, and shared cache.

Outcome: Shade rolled out to a large team. People sign in through your identity provider, membership follows your directory, the desktop app installs itself on managed Macs, and offices share a local cache.

Who it's for: IT and workspace admins at organizations with dozens to hundreds of Shade users. Some of these steps need an Enterprise plan.

Time: a few days, mostly spent waiting on identity provider and device-management changes.

Before you start

  • Decide whether you need one workspace or several. Large organizations with separate departments often want several workspaces under one organization with shared billing. Contact Shade to set that up. See Setting Up Workspaces and Drives.

  • Have admin access to your identity provider and your Mac device-management tool.

Checklist

1

Verify your domain and turn on SSO

Go to Settings > Enterprise, click Add domain under Domain Verification, and follow the steps. Then choose Set up SSO and pick your SAML provider. Once SSO is on, anyone with your domain signs in through your identity provider.

2

Sync membership with SCIM

Choose Set up SCIM in the same section. Members of the groups you provision are added to Shade automatically, and those groups appear in Groups with the type Directory. Make membership changes in your identity provider. Directory groups are read-only in Shade.

Every SCIM-provisioned user is a workspace member and takes a paid seat, so provision only the groups that need Shade.

3

Map groups to drives

Give each department its own drives, and grant access to the synced groups rather than to individual people. Set each drive's default inheritance deliberately. See Designing Your Permission Hierarchy.

4

Push the desktop app to managed Macs

Download the right Shade PKG for each Mac architecture (Apple Silicon or Intel), upload it to Jamf Pro, and deploy it with a policy. See Deploying the Shade PKG to Jamf Pro.

5

Open the right network paths

If your network filters outbound traffic, allow Shade's domains before rollout day. See Shade Network Configuration Guide.

6

Add a shared cache in each office

In offices where several editors work from the same footage, run a shared cache server on the local network. The first person to open a file pulls it from the cloud, and everyone after that gets it at LAN speed. See Using Shared Cache.

7

Turn on audit logging

Send Shade's audit events to your security tools. See Audit Logging and Shade SIEM Documentation.

Was this helpful?