Every tool a client asks me to approve gets the same four questions: who can get in, who can get out, what record exists of what they did, and what happens the day someone leaves. Most products answer two of those well and hand-wave the rest. Playbook answered all four without a six-week security review, which for a managed services shop is close to a miracle.
Access is the first. The client's creative team had been living in a shared folder tree where permissions drifted for years — a freelancer still had access to unreleased product photography eight months after the campaign ended. Board-level sharing with expiry dates replaced that. I can now answer "who outside this company can see the spring range" on one screen, and the answer is auditable.
Offboarding is the second. Single sign-on with directory provisioning means a departing designer loses access when their account is disabled, not when somebody remembers. We audited orphaned accounts across twelve SaaS platforms last year, and this was the only one with a clean list.
The activity record matters more than clients expect. During a scare in February — a vendor laptop stolen, nothing to do with this tool — I could pull who had downloaded the packaging files and when, which turned a speculative breach notification into a documented assessment. Legal appreciated it more than the design team did.
Then there's the boring benefit: restore requests. Version history is visible to creative staff, so "IT, can you get back the file from Tuesday" mostly stopped arriving — a handful of tickets a month that no longer exist.
Migration itself was a weekend. Bulk upload preserved the hierarchy, permissions were rebuilt Monday morning, and the team noticed little beyond a new login screen.
One caveat I'd insist on: this is storage and collaboration, not backup. We still run immutable snapshots elsewhere, because a sync tool deletes whatever your users delete. Review collected by and hosted on G2.com.
Deploying it was easy. What took months was the paperwork that followed, because a mid-market client with a legal department asks for things a creative storage product wasn't built to answer. Four requests came back unsatisfied, and each cost us a workaround.
First came a litigation hold. The client was responding to a human rights complaint involving a former employee, and counsel wanted every file that person had touched frozen. There's no hold function, so the instruction went out by email — nobody delete anything until further notice. That isn't a control, it's a hope, and the request arrived on a Friday.
Then the activity log: how long does it persist, and can it be exported? Shorter than the twelve months the client's cyber insurer wanted, and there's no feed into our log collector, so I capture screenshots monthly. For an audit trail that already proved useful in February, that's a weak foundation.
Legal wanted pre-launch imagery shared view-only, downloads blocked. Creative teams need outside photographers and retouchers to see work early; counsel wants those files un-savable. Watermarking and download restriction don't exist here, so the compromise is that those assets stay off the platform entirely and travel by encrypted transfer. The product loses the exact use case it's strongest at.
Nobody could explain what an exit looks like, either. Bulk import worked beautifully; export is another matter — boards, tags, and metadata don't survive in a usable shape, so leaving would mean rebuilding the hierarchy by hand. Vendors rarely volunteer that, but it belongs in the contract discussion.
One smaller operational gripe: the initial desktop sync saturated a 50 Mbps office line for most of a business day, with no throttle available.
None of it is fatal. But I describe it internally as excellent for the creative team and incomplete for whoever has to defend it in a review. Review collected by and hosted on G2.com.