Team management
Role-based access to every redirect, link and QR code. No server logins to share.
Invite marketing, SEO, developers and agencies with the role they need. Editors ship links, viewers read the numbers, managers run billing, and every change is recorded with who made it and from where.
3 members on Core. Unlimited members on Pro and Enterprise.
Members
Everyone with access to the My Brand workspace. One role per member.Members
Invite membersRole-based permissions
Four roles. Everyone gets exactly the access their job needs.
A role is set when you invite someone and can be changed in the members table at any time. Links, QR codes and domains are shared by the whole workspace, so there is nothing to hand over when people change jobs.
Ownerone per workspace
Everything, including deleting the workspace and transferring ownership to another member.
Manager
Team settings, billing and members, plus everything an editor can do. The role for team leads and finance.
Editor
Creates, edits and deletes links, QR codes and domains. No team settings, no members, no billing. The role for marketing, SEO and agencies.
Viewer
Sees links, analytics and team information, changes nothing. The role for stakeholders, clients and auditors.
Invite
Invite the whole team at once, with the right role from day one
Paste several addresses, pick a role, send. Each person signs in with their own account, so there are no shared passwords to rotate when someone leaves. Invitations that go unanswered can be resent or revoked from the pending list.
- Bulk invitations. Several addresses in one go, one role for the batch, individual roles afterwards.
- Resend or revoke. A pending invitation can be sent again or cancelled; revoking it only affects this workspace.
- Roles change inline. Promote an editor to manager in the table; no re-invite, no new login.
- Removal is immediate. Remove a member and their access ends at once. The links they created stay, with their name in the history.
Stop being the bottleneck
Marketing ships links on Friday evening. Nobody touches a server.
An editor creates redirects, branded links and QR codes in the dashboard and they are live worldwide in seconds. Anything that costs money or changes the plan stays with owners and managers, and the dashboard routes the request to them instead of blocking the work.
A member hits a plan limit
Editors and viewers cannot change the plan. One click sends the owner an email with the option they picked; what they typed is kept as a draft.
Finance pays without an account
A manager picks the plan and emails a 7-day checkout link to whoever pays. The payer needs no RedirHub login and pays by card.
Ownership moves with the job
When the person who set up the account leaves, the owner hands the workspace to another member. Nothing is re-created and no link goes dark.
Accountability
Know who changed what, and keep the accounts that can change it locked down
Change history on every link Pro Enterprise
Who changed it, when, the old and new value, and where the change came from: the dashboard, the API, an MCP client, a CSV import or auto-redirect. Editors and up can revert a single change.
On Core the number of changes is shown and the history unlocks with Pro. Enterprise adds a workspace-wide audit log.
Every account, properly locked
Each member protects their own sign-in. Two-factor authentication with any authenticator app, sign-in with Google or GitHub, and a list of the browsers signed in with the option to log the others out.
- Single sign-on (SAML). Sign in through your identity provider; when someone leaves the directory, their access goes with it. Pro add-on Enterprise · included
- Password checks. New passwords are scored for strength and checked against known breaches.
- Google or GitHub sign-in. Connect or disconnect them at any time; the last remaining sign-in method cannot be removed.
Agencies and multi-brand teams
One workspace per brand or client, one login for you
Each workspace has its own domains, links, members and plan. An agency keeps every client separate and switches between them from the sidebar; a client can be invited into their own workspace as a viewer and sees nothing else.
- Different roles in different workspaces. Owner of your own, editor at a client, manager at a partner, all under one account.
- Automation gets its own keys. Workspace API tokens with a name, a platform prefix and an expiry of 30 days to a year, plus a reminder a week before they run out.
- Same rules for the API and MCP. A token acts inside one workspace. Changes made through the API, an AI assistant or a CSV import land in the same history as dashboard edits.
- Tags for teams inside a workspace. Tag links by campaign, team or client and filter the list by tag, so a shared workspace still reads as separate projects.
Why roles, not shared logins
What changes when the whole team has an account
FAQ
