Roles and permissions

In Inperia, what each person can do is decided by their roles. A role brings together two things:

• Action permissions: what the person can do (see members, create meetings, take attendance) and which sensitive data they can see.
• Visibility scope: which people and records they can do it on (only themselves, their branch or the whole church).

Every member has at least one role, and can have several. If they have several, their permissions and scopes add up.

The owner

The owner isn’t a church role: it’s whoever manages the account. They can do everything, including billing, owners, the church network and support access, which only owners manage. Owners and account explains how.

System roles

Inperia comes with three ready-made roles, in Settings › Roles & permissions:

Role	Who it’s for	Scope over members
Pastor	The person who leads: almost everything in the church, except editing its details, billing and deleting someone for good	The member and their descendants
Leader	The person who walks alongside a group: manages the members in their branch and all the church’s contacts	The member and their descendants
Disciple	Every new member: sees their own information	Only the member themselves

Disciple is the Default role: the one a new person receives. For system roles you can change the name, the description and what they see on their dashboard. You can’t change their permissions or their scope, or delete them. The permission-by-permission detail is in the Permissions reference.

Create a custom role

When a system role doesn’t fit (someone who only takes attendance, someone who runs the church office), create your own:

1. In Settings › Roles & permissions, select New role. To start from another role, use Duplicate on that role, or Start from an existing role inside the form.

2. Enter the Name and the Description.

3. Tick the Action permissions, module by module. Each module’s Sensitive fields are ticked separately: the role only sees that data if you tick them.

4. Set the Visibility scope for each resource.

5. If the role takes attendance, set Whose attendance does it take?.

6. Choose What this role sees on its panel and save.

Then assign the role to people from their record, in the Role section.

Visibility scope

Each role sets its scope separately for each resource:

• Members: Only the member themselves, The member and their descendants, The member and their ascendants, Full branch, Branch + adjacent or All members.
• Contacts: Only my contacts or All contacts.
• Unassigned members, whom nobody leads yet: None, Only the ones they registered, The ones in their branch or Every unassigned member.
• Meetings, Follow-ups and Cell groups: their own, their own and their descendants’, those of their full branch, or all of them.
• Courses: Only the ones they teach, Theirs and their descendants’, Their whole branch’s or Every group, depending on who teaches each group. A person always sees the groups they teach.

Some actions require scope over All members: importing members, seeing and restoring archived members, merging records and deleting for good. With the system roles, in practice, the owner does these.

Whose attendance does it take?

For a role with Record who attended a meeting, set who it marks on the list: Whole church, With tags or Specific people, and whether they’re members only, contacts only, or both. With Only within its scope, it’s further limited to the people the role reaches.

The dashboard cards

What this role sees on its panel picks the blocks on the Dashboard. It doesn’t restrict access to the data: whoever has the permission still sees it in their lists. With Care turned on, the Need their attention card shows how many people are waiting for whoever has that role.

Rules that protect the church

• Nobody can create, assign or remove a role that grants more than the person doing it has.
• Permissions for the Churches and Billing modules can only be granted by an owner.
• A custom role can only be deleted if nobody has it assigned.

To manage roles, you need the Manage roles permission.