User Types & Roles

User types and roles are the same object in Orgo, separated by one setting called level. A role with the level User type is a membership category. A role with any other level is a position in your structure.

• User type: what kind of member someone is (Scout, Student, Honorary Member). One per member.
• Role: a position they hold (President, Treasurer, Troop Leader). A member can hold several, each with its own term.
• Permission: what they can do in the software. See Permissions.

Built for organizations whose members are not interchangeable, either because they pay different fees, see different menus, or fill in different forms. Replaces a “category” column in a spreadsheet and a separate document listing who holds which office.

---

​

Where it lives

Settings → Modules → Users & Profiles → Roles & User types, which requires the Orgo administrator flag on your account and appears when Enable Roles is on. Every role is listed with its plural name, a Level tag and any attached permissions. Filter by Level or Permissions, open the organisational chart, or press Add role.

---

​

Creating a role or user type

​

Extra settings on a user type

---

​

Assigning a user type

A member has exactly one user type; if someone fits two categories, pick the primary and use a role or tag for the other.

• On the member’s profile: Edit profile → Membership status → User type, then Save.
• When an admin creates a member: a user type selector on the create form.
• Automatically on registration: Default User Type After Registration stamps a type on every self-registration.
• From the registration link: signing up through /join/<slug> applies that type and the matching role.
• The applicant chooses: add the User Types field to the general registration form.
• On adhesion approval: approving an adhesion sets the type configured for successful applications, and emails the member if their type changed.
• Bulk import: set the type during a member import.

Changing the user type needs HR_LOCAL over the member’s chapter, and local admins must be allowed to change permissions (Allow Local Admins to Modify User Permissions, on by default) unless the person holds HR_TENANT. The Roles pane of the Edit view is offered to HR_TENANT, or to HR_LOCAL over the member’s chapter when chapters are on; adding roles there needs the same setting. See Member profile.

---

​

What a user type actually changes

• Fees: a type flagged Not eligible for fee, or the type chosen as fee-exempt, drops the member out of fee assignment entirely.
• Registration: each type can have its own registration form, public URL and preselected membership price.
• Menu: categories and items can be shown only to selected types. See Menu Organizer.
• Dashboard: widgets can carry a different image per user type. See Dashboard Builder.
• Directory: the member list can be filtered by type, subject to Who Can Filter Users by Type.
• Guest accounts: the type chosen as Guest User Type marks its members as guests; approving a resignation switches the member to it.
• Units: a unit type can require its members to hold a specific user type.

---

​

Roles and terms

Assign a role from Edit profile → Roles → Add role: choose a scope (the organisation, Chapter or Units), tick the roles and Save. Each assignment has a Date begin and an optional Date ended. The member’s roles are drawn as one timeline, Now above History, on the profile’s Roles card and in the Roles pane. To end a role, press End role on its row, confirm the date and Save. Ending a role ends the permissions it carried, and the assignment moves to History. Dates can be corrected afterwards by clicking the row, and a record entered by mistake can be deleted from the history. That is why permissions belong on roles rather than people: a handover is one assignment ended and another started. The steps in full are in Member profile. Where each level applies: Organisation is the whole organization, Chapter one local center, Parent chapter a parent local center and every local center beneath it at any depth, a unit type a specific unit or team of that type, and None a label with no scope and no permissions. A chapter role attaches to the member’s own chapter when assigned. A parent-chapter role attaches to the member’s own chapter when that chapter is flagged It’s a parent chapter, and otherwise to the chapter directly above it, never higher. A member whose chapter is neither a parent nor has one cannot hold a parent-chapter role at all. Role Groups can also fill groups from role, age, gender, chapter, region or fee tier with no manual assignment.

---

​

Settings reference

Under Settings → Modules → Users & Profiles → Configuration.

---

​

Common questions

---

​

Related

• Permissions: what each permission level unlocks
• Registration Form: per-type forms and public sign-up links
• Role Groups: groups that fill themselves from roles and member data
• Organizational Chart: the structure your roles produce
• Adhesion: assigning a type when an application is approved