IP Protection for Design Agencies: What to Reclaim When a Contractor Leaves

When a contractor leaves your design agency, two things need to happen simultaneously: access revocation and IP ownership confirmation. Most agencies handle neither correctly. They forget to remove the contractor from Figma and Adobe Creative Cloud, and they never secured a copyright assignment, which means the designer legally owns the work they were paid to create. This guide covers both layers in one checklist.

Disclosure: this is the Optserv blog. We write about access lifecycle and agency operations. Where relevant, we mention Optserv, but this guide covers practices that apply regardless of what tools you use.

Why Design Agencies Are Especially Exposed

Design agencies run on client IP. Your Figma files, brand assets, motion graphics, and source files are what your clients paid for and what you sell. When a contractor cycles out, and at most agencies, turnover runs 20–30% per year, that IP and access both walk out the door unless you've built the right exits.

The pattern is almost always the same: a senior designer joins for a 3-month campaign, gets added to six client Figma files and the team Adobe Creative Cloud plan, delivers the work, and leaves. Six months later, those accounts still exist. Nobody removed them at project end, because removing them was never explicitly someone's job.

The Access Layer: What to Revoke First

Start with tools, not contracts. Even if IP ownership is resolved, active access is the immediate risk.

Figma

If you're on a Figma Organization or Professional plan, go to Settings → Members and remove the contractor. Before you do:

1. Transfer ownership of any files they created. Right-click the file in the file browser → Share → click the dropdown next to their name (shown as "Owner") → select Transfer ownership to your team account.
2. Check all team workspaces, contractors are often added to individual project workspaces beyond the main team.
3. Confirm that client files live inside your organization, not in a personal file the contractor controls. If a file was created in their personal Figma account and shared via link, the admin transfer path doesn't apply. You need the contractor to initiate the transfer while you still have contact, or duplicate the file into your org.

That last scenario is the most common failure mode: a contractor creates the file in their personal workspace, shares the link, and the agency never acquires org-level ownership.

Adobe Creative Cloud

Manage licenses through the Adobe Admin Console (adminconsole.adobe.com). Under Users, find the contractor and select Remove User. The license is reclaimed automatically and the seat becomes available for reassignment.

Before removing:

• Download or transfer any Creative Cloud Libraries the contractor built for your brand (logos, color swatches, character styles). These live in their account.
• Retrieve any fonts enabled via Adobe Fonts that your team now depends on: those are tied to the license, not the file.

Canva

In Canva Teams, go to Settings → Members and remove the contractor. There is no robust file ownership transfer flow in Canva, so download or duplicate any designs they created before you remove them. Once removed, access to their designs inside your team workspace is lost unless you've already duplicated them.

Shared Drives and Other Tools

Google Drive shared folders, Dropbox Business, and Notion workspaces all require manual removal. Check shared drive membership as well as individual folder shares: contractors are frequently added directly to client folders, not just the top-level shared drive.

Portfolio Platforms: Dribbble, Behance, Contra

You cannot force a contractor off their personal Dribbble or Behance account: those are personal platforms, not ones you control. What you can control is whether they're allowed to show your client work there. This is a contract question, not an access question (covered in the IP section below).

For platforms your agency does control, an agency Behance organization account, a shared portfolio site, remove them through that platform's admin settings.

Verification Step

After completing tool revocations, cross-check by searching the contractor's work email in each tool's admin panel. Google Workspace, Slack, GitHub, and Notion all support email lookup in their admin or members views. Any result means an active access path you missed.

For a structured approach to discovering all access paths, see The Agency Contractor Access Audit Checklist (Run It in 20 Minutes).

The IP Layer: Who Actually Owns the Files

Revoking access gets you security. It doesn't give you legal IP ownership.

In most jurisdictions, including the US, UK, Singapore, and most of Southeast Asia, a freelance contractor owns the copyright to the work they create by default, even if you paid for it. Work-for-hire doctrine under US copyright law applies only to employees, not independent contractors. For contractor work to legally become your IP, you need a written assignment.

This surprises most agency owners. You commission a logo redesign, pay the invoice, receive the Figma file, and the designer still owns the copyright. They could theoretically prevent you from using it, or license it to someone else. In practice, most contractors don't enforce this. But "they probably won't enforce it" is not a legal position you want to rely on when a client relationship or acquisition is on the line.

The fix is straightforward: a copyright assignment clause in your contract, signed before work starts.

Copyright Assignment in the Contract

Your contractor agreement should include:

1. Work-for-hire / assignment clause: All work created under this agreement, including all source files, designs, and deliverables, is assigned to [Agency Name] upon payment.
2. Scope of assignment: Covers all derivative works and modifications.
3. Moral rights waiver (for UK and EU contractors): The contractor waives any moral rights in the work to the extent permitted by law.
4. Confirmation on exit: At end of engagement, the contractor confirms in writing that all IP created has been transferred and no copies are retained.

If your current contracts don't have this, add it to all new contractor agreements going forward. For existing contractors mid-engagement, a simple IP assignment addendum signed before the next project starts covers you.

Portfolio Rights Clause

Unless your contract says otherwise, contractors can display client work in their portfolio, they're the copyright holder. If you handle sensitive brand work or have NDAs with clients, add a portfolio rights clause:

• Restricted: Work may not be shown publicly without written approval from the agency.
• Permitted with credit: Work may be shown with specific attribution wording pre-approved by the agency.
• Confidential client carve-out: All work for [Client Name] is confidential and may not be shown publicly under any circumstances.

Build the Exit Before the Start

The most common reason agencies lose control at contractor departure is that access and IP weren't structured at the start. Here's how to set it up right from day one.

Use Organization-Level Accounts, Not Personal Ones

The Figma file ownership problem only exists when contractors create files in their personal accounts. Prevent it by provisioning access through your Figma Org plan and requiring contractors to work inside your team workspace from day one. Same for Adobe CC: issue licenses from your Admin Console with named-user seats, not shared passwords.

Shared Creative Cloud passwords are surprisingly common in small agencies. When the contractor leaves and you change the password, it breaks access for everyone still using it. Named-user licensing solves this.

Project-Scoped Access Only

Don't add new contractors to all client files. Add them to the specific project workspace they need. When the project ends, removing them from that workspace is the entire offboarding action, no audit needed.

Get IP Assignment Signed Before Work Starts

IP assignment is hardest to negotiate after the work is done. The contractor has leverage: you need the files. Get it signed as part of onboarding, alongside the NDA and rate agreement.

Many standard contractor templates from online legal services cover payment terms and confidentiality but treat IP as a separate topic. Check yours and add a clause if needed.

For the moment when a project closes and you need to revoke access fast, see When the Project Ends: How to Revoke Contractor Access Before the Agency Gets Burned.

Centralize Your Contractor Roster

You can't run a proper offboarding if you don't know who's currently active. Keep a running list of active contractors, the tools they have access to, and the client projects they're assigned to. Update it when they start, update it when they end.

This doesn't require a full HRMS. A Notion database or spreadsheet works for a 10-person agency. The key is that someone owns it and it's kept current.

Design Tool Offboarding: Quick Reference

Note: file transfer handles the account layer. A signed copyright assignment is still required to establish legal IP ownership.

FAQ

Who owns the design work a contractor created if I paid for it?

By default, the contractor owns the copyright under most legal frameworks, including US copyright law. Work-for-hire doctrine applies to employees, not independent contractors. The fact that you paid for the work doesn't transfer ownership. To legally own the IP, you need a written copyright assignment clause in the contractor agreement, executed before or at the start of the engagement.

How do I transfer a Figma file to my agency account?

In the file browser, right-click the file and select Share. In the sharing panel, click the dropdown next to the contractor's name (shown as "Owner") and select Transfer ownership, then confirm. This only works for files within your Figma organization. If the file was created in the contractor's personal Figma account and shared to your team via link, you can't use the admin transfer path, the contractor needs to initiate the transfer directly, or you need to duplicate the file into your organization workspace using Duplicate to your drafts and then move it to the team.

Can a contractor add my client's design work to their portfolio?

Unless your contract says otherwise, yes. Independent contractors generally have the right to display their work publicly, and in most jurisdictions they hold the copyright until it's formally assigned to you. If you want to restrict portfolio use, especially for confidential client work, add an explicit clause before work starts. Trying to add this restriction after delivery is difficult: the contractor has the files and the leverage.

What should be in my contractor agreement to protect design IP?

At minimum: (1) a copyright assignment clause transferring all work created under the agreement to the agency upon payment, (2) a scope clause covering source files, derivatives, and modifications, (3) a portfolio rights clause specifying what the contractor can show publicly, and (4) a confirmation-on-exit acknowledgment where the contractor confirms no copies are retained. For UK and EU contractors, add a moral rights waiver. Have a lawyer review it once, a generic template with these clauses added manually may have gaps depending on your jurisdiction.

Try Optserv

Optserv handles the contractor lifecycle layer that design agencies consistently drop: from access provisioning on day one to a structured offboarding flow that hits all tools at once. When a contractor's engagement ends, you trigger one offboarding flow and Optserv revokes access across Figma, Slack, Notion, Google Workspace, and the rest of the stack simultaneously, no spreadsheet, no manual chase. It also maintains the contractor roster so you always know who's active and what they can access.

Start free at app.optserv.ai →

Sources

• Figma Help Center, Transfer ownership of files or projects
• Adobe Admin Console: User management and license reclaim documentation
• Rocket Lawyer, Can a contractor show my project in their portfolio?
• TechAssist, IT Support for Creative and Marketing Agencies, named-user licensing + freelancer offboarding practices
• Accountable HQ, Offboarding Access Controls Checklist