Knowella

Roles — how they work, create & edit

Define what people can build, assign, and approve — and keep that model up to date.

3 min read Real product screens
app.knowella.com Live walkthrough
Roles decide what a user can see and do — which apps, which actions, which data. Defining them here means access is consistent across every app the company runs, instead of being configured app by app.
In this article

How roles & permissions work

A role is a bundle of permissions — build, assign, approve — that applies the same way wherever it's granted, so a person's access doesn't have to be reasoned about differently from one app to the next.

Create a role

When an existing role doesn't quite match how a group of people should work, name a new one and set the permissions it carries — what it can build, assign, and approve. It's ready to assign to any user right away.

Edit a role

As a process changes — a new app, a new approval step — open the role and update what it can build, assign, or approve. Everyone currently holding that role picks up the change immediately, with nothing to reassign by hand. Roles aren't deleted once created — they're kept and adjusted in place, so nothing that references them breaks.

Why it matters

A consistent, well-kept permission model is what makes human approval meaningful rather than decorative — it's always clear who's actually allowed to sign off on what.

Ready to build your own?

Start free and ship your first app in minutes — or have us set it up with you.