Roles & permissions

Permissions are per guild. A role is a bundle of them, and a member can hold several roles at once.

The four default roles

Every new guild is created with these, already wired up:

Role	Can do
Guildmaster	Everything. The guild's creator gets this automatically.
Officer	Read everything; create and edit members, events and renown. Cannot edit the guild itself or its roles.
Member	Read-only across the guild: guild, roles, members, events, renown.
Guest	Read the guild, its events, and enough member data to see who is participating.

You can rename them, change what they grant, add more, or delete the ones you do not want — nothing depends on the default names except the Guildmaster assignment at creation time.

How a permission is built

One permission is three things together:

A resource — what it applies to: Guild, Role, User, Event or Renown.
A command — what you may do to it: Read (see it), Edit (change existing ones) or Write (create and delete).
A game scope — All Games, or a specific list. This is how you give someone authority over your WoW raids without giving them anything in your FFXIV section.

Edit and Write are separate on purpose. Edit lets someone fix an existing event; Write lets them create and delete events. A "trusted but not in charge" role usually wants Read + Edit and no Write.

Managing roles

Guild → Manage → Roles. The table shows how many Read / Edit / Write permissions each role carries and which games it covers — a globe icon means all of them.

Create role — give it a name and a description. It starts with no permissions.
Click the role to open it. The Details tab holds a permission grid; press Edit on it, tick the boxes you want, then Update Permissions.
The Users tab lists every guild member with Assign role / Remove Role buttons.

Deleting a role removes it from everyone who holds it — the role page warns you before it does.

Assigning roles

Three moments where roles get handed out:

From the role's own Users tab, at any time.
When accepting an application — you must pick at least one role before the accept goes through.
When sending an invitation — the roles are chosen up front and applied the moment the person accepts.

What permissions change on screen

TRAX follows one convention consistently, so you can read the UI as a permission report:

Standalone create buttons are hidden when you lack the permission — no Create Event button at all.
Row-level Edit / Delete buttons are disabled, not hidden, so you can still see that the action exists.
Whole tabs disappear. Manage only shows up if you can edit members, read roles, or edit the guild; each sub-tab has its own check.

If a button is missing, it is a permission — not a bug. Ask a Guildmaster to check the role grid before reporting it.