Temporary Participants and Reviewed Players

You do not need to build a complete roster before arranging every appointment. The managed Castle planner can include a temporary participant: a named person attached to this schedule, without creating a kingdom or alliance player.

Add someone just for this schedule

Use Add player manually on the relevant slot and choose the temporary-player option. Enter a clear display name and, if useful, a private organizer note. Check the Temporary indication before saving.

The assignment remains part of the managed schedule and follows its save and publication workflow. "Temporary" describes the participant's identity, not browser-only storage: this person has no linked roster player or application. The label does not add alliance membership, account access, or player history.

Keep public labels suitable for everyone who can see the schedule. Private notes are for authorized organizers; do not put sensitive details into the name that participants will see.

When approval should update the roster

An application needing identity review follows a different path. The reviewer checks the selected kingdom and alliance, player name, and in-game ID before approving it.

When approval resolves a valid identity, the system can create a missing roster player or update the name on the matching existing player. A matching in-game ID takes precedence over assuming two similar names are the same person. Ambiguous or conflicting matches must be resolved before approval.

This review is the point at which roster changes are authorized. Merely typing a name into an application, or creating a temporary schedule participant, is not the same action.

A practical example

An organizer wants to include a visiting player for one appointment. They add a temporary participant and publish the reviewed schedule; the visitor does not become an alliance member.

Later, a genuine alliance member applies under a changed nickname. The reviewer confirms the existing in-game ID and approves the application against that player. The roster name can be updated without creating a duplicate identity.

Approval is not an appointment

After approval, refresh or reopen the relevant candidate if its state has not yet updated. Eligibility makes scheduling possible; it does not guarantee that the requested time is free. Assign the candidate, validate the draft, and publish before treating the time as confirmed.

For a plan with no shared records at all, use the separate Local Castle Planner. For the full workflow, continue with review and planning and publishing.