Roles and access
Inviting your team, what each role can reach, and the actions we run on request.
Everyone who touches the app needs their own login. Shared accounts make the audit trail useless and cost you an afternoon when someone leaves.
Inviting an admin
Invite admin, then the email address. They get an invitation and set up their own account.
Invite the people who will run the community day to day.
Roles
| Role | What it can reach |
|---|---|
| Admin | Quests, events, submissions, members, rewards, the store and the newsfeed. The normal role for a community manager. |
| Content Creator | Posts and settings only. Built for a creator or a social manager who publishes to the newsfeed and should not be able to change your economy. |
Put at least two people on Admin, so a holiday does not block a launch.
Sub-roles narrow this further when you want a reviewer who only handles submissions or a marketer who only touches the newsfeed. Ask us for the split you want.
Actions we run on request
A few changes sit outside those roles and we make them on your community when you ask. Tell your FanBase contact what you need and we run it. Ask for the turnaround when you ask for the change, because it varies with the action.
If a button you expected is not there, this table is the first place to look.
Finding people
The admin list carries each person's in-app username, their Discord handle and the date they joined. Search by username, or filter by join date to find whoever was added during a campaign and never removed.
Review the list every quarter. Agencies rotate staff, and an admin account nobody remembers creating is the one that publishes a draft by accident.