The moment more than one person manages links — an agency with clients, a team with a contractor, a founder handing the keys to a hire — the question stops being "can they create a link?" and becomes "can they see each other's links?" Projects are the answer: a way to group domains and hand out exactly as much access as each person needs.
The shape of a project
- One owner — the account that created it (an agency, usually). Owners can rename the project, add and remove people, and move domains in or out.
- Members — see and work with every domain assigned to the project, and nothing outside it. A member of the Acme project has no idea the Foundry project exists.
- Sub-admins — members who can also manage people and domain assignments, so day-to-day administration doesn't always route through you.
Tightening the screws per project
Each project carries three switches the owner can flip for plain members: whether staff may edit redirects, delete redirects, and manage domain-level settings. A typical agency setup: clients get view-and-create on their own project with deletes off, so a well-meaning click can't take a live campaign down.
Why this beats sharing one login
- Everything is attributed. Every change is logged to the person who made it — including transfers and deletions.
- Offboarding is one click. Remove someone from the project and their access ends that instant; their account (and any other projects) is untouched.
- Ownership can move. A whole project — domains, links, members — can be transferred to a client's own account when they outgrow you. Bittersweet, but clean.
Domains are assigned to at most one project, which keeps the question "who can touch this domain?" answerable at a glance. If you're managing client domains at any scale, projects turn that from a spreadsheet into a settings page.