Builders and permissions

Builder access belongs to one world. Adding someone as a builder in one world does not grant access to any other world.

The world’s author is treated as rank 4. Rank 3 and rank 4 builders can open World > Config, find World Builders, and select manage to add an existing Written Realms Alpha account by email address.

Builder ranks

Use the lowest rank that supports the person’s work:

Rank	Visibility and editing	Builder management
1	Works only with assigned zones, rooms, item templates, and mob templates.	Cannot add builders.
2	Can inspect content entities throughout the world, but can edit only assigned zones, rooms, item templates, and mob templates.	Cannot add builders.
3	Can inspect and edit all world content, including world configuration.	Can add builders at rank 1 or 2. Cannot create or set rank 3 or 4 access.
4	Author-equivalent access to the world.	Can create and set every builder rank, including rank 3 and 4.

Rank 4 is author-equivalent

A rank 4 builder can do anything the author can within the editor. Reserve it for someone who should have full control of the world and its other builders.

Rank 3 is also broad editorial access, not a scoped senior assignment. Although it can manage lower-ranked collaborators, only rank 4 can grant another person rank 3 or rank 4.

Add a builder

1. Open World > Config.
2. In World Builders, select manage.
3. Select Add World Builder.
4. Look up the existing user by email address.
5. Choose a rank and save.
6. For rank 1 or 2, open that builder’s Manage Builder Assignments link and add the required scope.

Adding a rank 1 or rank 2 builder without an assignment does not give them a useful editing area. Add the assignment as part of the same handoff.

Assign scoped work

Assignments are available for four entity types:

Assignment	Scope it grants to rank 1 or 2
Zone	The zone and its rooms, plus zone-scoped work such as paths, loads, and quests. Use this when someone owns a whole area.
Room	One room and its room-level details, loads, checks, actions, flags, and exits. It does not grant the rest of the zone.
Item Template	One item template and its template-specific configuration.
Mob Template	One mob template and its template-specific configuration.

Rank 1 sees a deliberately narrow work area. Rank 2 is useful when a collaborator needs to read the rest of the world for context while remaining unable to edit outside assigned scope. Rank 3 and rank 4 do not need assignments because their edit access is world-wide.

When a rank 1 or rank 2 builder creates a zone, item template, or mob template, the editor records an assignment to that new entity automatically. Do not assume that makes related existing content editable; review the assignment list after reorganizing a zone or handing off templates.

Note

Assignment checks follow the underlying entity. A zone assignment is broader than a room assignment, while item and mob templates remain separate even when a room loads them. Assign each template explicitly when a scoped builder must edit it.

Choose a rank and scope

A practical least-privilege pattern is:

• Use rank 1 + room or template assignments for a narrowly defined contribution.
• Use rank 1 + a zone assignment for ownership of one self-contained area.
• Use rank 2 + assignments for a collaborator who needs world-wide reading context or review access.
• Use rank 3 for a trusted co-builder who must change configuration and content across the entire world.
• Use rank 4 only for an author-equivalent partner who must also grant high-level access.

Keep boundaries easy to explain. A single zone assignment is usually clearer than a long list of individual room assignments when the builder is responsible for the entire zone.

Working on small screens

On a narrow or mobile screen, the editor moves its side navigation below the main content and hides the direct Admin, Builders, Players, and Factions shortcuts. This does not change the builder’s rank.

A rank 3 or 4 builder can still open World > Config and use the World Builders management panel there. For substantial map or configuration work, a wider screen makes the navigation and room topology easier to review.

Collaborate safely

Permissions limit who can change an entity; they do not merge simultaneous edits or explain a teammate’s intent. Before several builders work at once:

1. Divide responsibility by zone or template.
2. Record conventions for names, keywords, coordinates, and internal notes.
3. Tell teammates before moving rooms, changing exits, or deleting a referenced template.
4. Recheck assignments after moving a room to another zone or changing ownership.
5. Playtest connected work as an ordinary character before making the world public.

Continue with Rooms and exits for the core map workflow and World settings for the controls reserved to rank 3 and rank 4.