This article explains what each role in Templified can do, so you can set up your team correctly from the start.
The three roles
Every member of an organization has one of three roles: Owner, Admin, or Designer. Roles appear as badges on the Settings → Members page.
| Capability | Owner | Admin | Designer |
|---|---|---|---|
| Create and edit templates | Yes | Yes | Yes |
| Work in Studio (create designs, render, send) | Yes | Yes | Yes |
| Create custom Send-To preset groups | Yes | Yes | Yes |
| Open Flows and build, edit, or run a flow | Yes | Yes | Yes |
| View the Activity delivery log and replay a delivery | Yes | Yes | Yes |
| Manage the Connection and Routing tabs in Flows | Yes | Yes | No |
| See example values from real deliveries while building a step | Yes | Yes | No |
| Manage integrations (Dropbox, GFcrew, webhook) | Yes | Yes | No |
| Create, edit, and delete Send-To presets | Yes | Yes | No |
| Manage the Default Send-To preset group | Yes | Yes | No |
| Manage print locations | Yes | Yes | No |
| Invite members and manage roles | Yes | No | No |
| Remove members | Yes | No | No |
| Update organization name and settings | Yes | No | No |
| Billing (add card, fund balance, auto-refill) | Yes | No | No |
| API Keys | Yes | No | No |
How roles split up Flows
Everyone can build, edit, and run flows, and everyone can open the Activity tab to see which photos arrived and replay a delivery that didn't produce what it should have. Two parts of Flows stay with owners and admins, for reasons that are about safety rather than seniority:
- Connection and Routing — the Connection tab shows the private address that lets photos into your organization. Anything sent to it starts a run you're billed for, so only owners and admins can view, regenerate, or revoke it, and only they decide which flow an incoming photo is routed to.
-
Example values while building a step — a delivery can carry personal details about other people, such as a parent's phone number or a player's name. When a Designer builds a step, the variable picker still lists every field name that has arrived, so tokens like
{teamName}work exactly as they do for an admin — but the small preview showing what a token resolved to on a real delivery appears only for owners and admins.
Designer — create and send
The Designer role is the default for everyone you invite. Designers can do all the day-to-day work: edit templates in the template builder, open Studio to create and edit designs, run renders, and send finished images to any destination that has already been configured. They cannot change how integrations or Send-To presets are set up.
In Flows, a Designer can do the everyday work end to end: build a flow, run it, and check the Activity log to confirm a photo arrived — replaying it themselves if it didn't, without waiting on an admin. They can't open the Connection or Routing tabs, and they don't see example values from real deliveries while configuring a step.
Designers can create their own custom Send-To preset groups to organize the preset list for their own workflow, but only owners and admins can edit the Default group or create and delete presets themselves.
Admin — manage integrations and send-to without full ownership
The Admin role gives a team member everything a Designer has, plus control over the organization's integrations and Send-To configuration — without handing over billing or member management. Use this role for a studio manager or lead who needs to:
- Connect or disconnect integrations in Settings → Integrations (Dropbox, GFcrew, webhooks).
- Create, edit, and delete Send-To presets in Settings → Send-To Presets.
- Manage the Default Send-To preset group.
- Add, update, or remove print locations in Settings → Print Locations.
- Set up how photos reach your flows: the Connection and Routing tabs in Flows. Admins also see example values from real deliveries when configuring a step, which Designers don't.
Admins cannot invite or remove members, cannot change anyone's role, and cannot access Billing or API Keys. Those capabilities remain with the owner.
Owner — full control
There is one owner per organization. The owner has every Admin capability, plus:
- Billing — add a card, fund the balance, configure auto-refill, and view the full usage ledger. The Settings → Billing page is visible only to the owner.
- API Keys — create and revoke API keys. The Settings → API Keys page is visible only to the owner.
- Member management — invite people by email or invite link, change any member's role (Owner, Admin, or Designer), and remove members.
- Organization settings — update the organization name and other general settings in Settings → General.
Ownership can be transferred: go to Settings → Members, open the menu on any Admin or Designer, and change their role to Owner. You'll be prompted to confirm, because this demotes your own account to the selected role.
Inviting someone and setting their role
- Go to Settings → Members.
- Under Invite Members, enter an email address and click Invite — or click Generate invite link to copy a link you can share any way you like.
- New invitees join as Designer by default. Once they accept, open their menu in the member list and select Change role → Admin if needed.
Pending invitations appear below the invite form and can be revoked before they're accepted.
Comments
0 comments
Article is closed for comments.