Admins, editors and roles explained
Who can do what in an organization, a challenge and a community: Owner, Admin, Editor and Member, and how to hand out roles without chaos.
Yazan: MyGritWall ekibi4 dk okuma
Bu makale İngilizce olarak sunuluyor.
The short answer: give people the fewest rights they need to do their part. In an organization, one Owner holds billing and the final say, Admins run people, rules and approvals, Editors create and run challenges, and Members take part. Challenges and communities have their own, smaller set of roles: an Owner, a few Admins and the members. Always have a second Admin so nothing stalls when someone is on holiday.
Roles sound like an administrative detail until something goes wrong: a proof nobody can approve, a challenge that only one person could have cancelled, or a former colleague who still has the keys. A little thought at the start prevents most of that. This guide explains the roles in MyGritWall and gives practical advice on handing them out.
A few principles before the details
- Fewest rights needed: start people low and raise their role when they need it.
- No single point of failure: at least two people can approve, moderate and invite.
- Roles follow tasks, not seniority: the person running the walking challenge needs more rights than their manager does.
- Review roles when people change jobs or leave, not once a year.
These principles apply at every level. The same person can be a Member of the organization, the Owner of one challenge and an Admin of a community, and that is perfectly normal.
Organization roles
An organization has four roles: Owner, Admin, Editor and Member.
- Owner: “Everything, including billing, Admins and deleting the organization.” There is exactly one Owner.
- Admin: “Runs the organization: people, rules, approvals and insights.” Admins invite, manage and remove members, handle settings, domains, policy and moderation, see insights, reports and the audit log, manage the team library, approve proofs, and can cancel or delete any organization challenge.
- Editor: “Creates and runs challenges and manages teams.” Editors create organization challenges and communities and edit and run organization challenges. They do not approve proofs or moderate, and cannot cancel or delete challenges they do not own.
- Member: takes part, posts and comments.
Most people should be Members. Make the colleagues who organize activities Editors, and keep the Admin group small: people from HR, the wellbeing lead, and a deputy.
Handing over the organization
Because there is only one Owner, plan the handover before it is urgent, for example when the person who set up the trial changes teams.
- Agree with the new Owner that they will take over billing and the final say.
- Make sure they are already an Admin, so they know the settings.
- Start the transfer from the organization’s settings.
- Wait for the new Owner to accept; nothing changes until they do.
- After acceptance, the previous Owner becomes an Admin and can stay on to help.
Challenge roles
Every challenge has its own roles, separate from the organization: Owner, Admin and Member.
- Owner only: cancel or complete the challenge, delete it, manage Admins and transfer it.
- Owner and Admins: edit the challenge, approve joins and proofs, moderate, use the comments switch, manage teams, invite links and members, pin and announce, and turn on “Allow joining after the start”.
- Members: take part, check in, post and comment.
For a challenge with more than a handful of people, add one or two Admins. Proofs and join requests get answered faster, and the Owner can take a day off without the challenge stalling.
Community roles
Communities also have Owner, Admin and Member.
- Owner: “Runs the community, hands it over or deletes it.”
- Admin: “Invites, approves and removes members.” Admins also change the cover, start challenges in the community and post announcements. They can remove plain members only, not other Admins.
- Members: post and take part.
A community with an active Admin team feels alive. Two or three Admins who share the welcome posts and the occasional announcement are usually enough.
Common mistakes to avoid
- Making everyone an Admin “to be safe”, so nobody knows who is responsible for what.
- Leaving one person as the only one who can approve proofs, then wondering why check-ins wait for days.
- Forgetting to change roles when someone moves to another team or leaves the company.
- Giving an Editor role to someone who only wants to take part, which hands them rights they will never use and nobody remembers giving.
When you are unsure, ask what the person actually needs to do this month. If the answer is “take part”, Member is the right role, and you can always raise it later.
Where MyGritWall fits
In MyGritWall, these three layers fit together. The organization decides who can create and run things across the company, each challenge decides who runs that challenge, and each community decides who looks after that group. Organization Admins can also cancel or delete any organization challenge, which matters when a challenge needs to be closed and its Owner is not around.
A sensible setup for most companies: one Owner, two or three Admins, an Editor for each person who organizes activities, and everyone else as a Member. Each challenge gets its Owner plus one Admin as a backup.
Kontrol listesi
- Most people are Members; roles are raised when needed.
- There are at least two Admins in the organization.
- Each busy challenge has an Owner and at least one Admin.
- Ownership is handed over before it becomes urgent.
- Roles are reviewed when people change teams or leave.
- Community Admins share welcome posts and announcements.
Good roles are mostly invisible: proofs get approved, questions get answered and nothing depends on one person. Start people with the fewest rights they need, add a backup for every key task, and review roles when your team changes. When you are ready, set up an organization and invite your first Admin.
Kişilerin için bir mücadele başlat
Bir hedef koy, birkaç görev ekle ve tek bir bağlantı paylaş. Ücretsiz bir mücadeleye katılmak ücretsiz kalır.