Blog · August 4, 2026 · Rich Chetwynd
Who can do what: roles on Croft
Owner, Admin, Creator, Member - a small, clear set of roles for giving your team the right access without turning it into a security project.
As soon as more than one person is building on a croft, you need to answer a simple question: who can do what? Croft keeps the answer small. Everyone you invite has exactly one role, and there are four of them.
Owner - the person whose croft this is. Full control, including billing. There’s always exactly one.
Admin - a trusted helper who manages the croft day to day: creating and approving connectors, inviting and removing people, building apps. Admins can do almost everything except billing and handing over ownership.
Creator - someone who builds and ships their own apps without managing the whole account. They can create, deploy, and share the apps they own, and request access to a connected data source - but they can’t create connectors or approve grants themselves.
Member - someone invited to use the apps that are shared with them. No building, just using.
That’s the whole model. It maps onto the two moments that actually matter on a team: the day someone joins, and the day someone leaves. Add a person once and pick what they can open; remove them once and they’re out of everything, instantly.
Roles are also what make data governance work. A Creator can build an app that asks to use the payroll connector, but it stays switched off until an Admin says yes - and the whole thing is on the record. Least privilege, without a spreadsheet of permissions to maintain.
Change someone’s role any time from the People page.
Your team’s first app could be live tonight.
Free for a day, and a week once your first app is live. No card needed.
Free to try. No card needed.