Roles and access

Where: Setup → Members

Access on TogoActive is granted per event. Being added to one event gives someone nothing on any other — there is no account that quietly sees everything.

Adding someone

Setup → Members, add them by email, choose their role. They get access the next time they sign in.

If they do not have an account yet, they create one first — including through Google sign-in — and you add them once it exists.

What roles control

A role decides which sections of the admin panel a person can open, and whether they can change what they see or only read it.

The practical distinctions:

• Full access — every section, including payments, participant data and the danger zone.
• Limited access — some sections only. Typically used for people who write content or answer participant questions but should not see financial data.
• Read-only — can look, cannot save.

Sections a person cannot access do not appear in their sidebar at all, rather than appearing and erroring.

Content permissions are separate

Website content has its own, finer-grained permissions, split by surface — someone can be allowed to edit pages without being allowed to change the event's settings. If you are giving someone access purely to write copy, this is what you want, rather than full access.

Who to give access to

The useful rule: payments and participant data are the sensitive parts. Everything else is recoverable.

• A designer working on the site needs content access, not full access.
• Someone answering participant emails needs to see participants, and usually nothing else.
• Only people who are accountable for the money need payments.

Removing access

Remove them from Setup → Members. It takes effect immediately.

Do this when someone leaves the project. Access does not expire on its own.

Removing access does not undo their work

Deleting a member removes their ability to make further changes. Anything they already changed stays changed.