Depending upon their role, users have varying degrees of access to the site.
|1||Manager||User trustworthy enough to have access to the whole site, and has the opportunity to be the master manager who can change any site element and assign editing tasks|
|2||Writer||Eligible for performing editing or review tasks assigned by the master manager|
|3||Guest||Passive role with full view access to the site. Not meant for production sites, but for demonstration sites that can be used for training|
A manager automatically becomes the master manager when they are the first manager to log in after the previous master manager clicked the Log out button on the Work list page, or after their 20 minute timeout has elapsed.
Managers have the potential to run the site or ruin it, so they are meant to be someone who understands what the site is for and can provide responsible stewardship. That means that one's teenage niece or nephew that can do a bit of web programming, but whom you wouldn't trust with your bank account, is unlikely to be a good manager.
The writer role is suitable for contractors, by providing access only for editing or reviewing a particular article. Guest roles are not for a real person, but a role that allows multiple-person access for viewing almost all the pages of a demonstration or leaning site. Guests cannot see the Email field contents for other users. Typically, such sites would have a single token manager user for setting up and managing the site.
If a guest account is created with an ID of gu, its password can be made available in an article using the Guest password option of the site value element. This allows for a site to be publicly accessed for demonstration purposes.
All users have the same basic details.
|1||ID||Short user identifier used for logging in. Must be unique. Can be changed by the user or the master manager|
|2||Full name||Full user name, for when credited with authoring in the footer of articles. Can be changed by the user or the master manager|
|3||Known as||Name used as a salutation in notification emails. Can be changed by the user or the master manager|
|4||Email address required for notifications. Can be changed by the user or the master manager|
|5||URL||Optional web site URL for making the author name into a link. Can be changed by the master manager|
|6||Accessibility||Personal accessibility setting for the user when using management pages. Can be changed by the user or the master manager|
|7||Expiry||Date user will be disabled. Managers are never expired. Master manager can extend by set periods|
|8||Role||Current role. Can be changed by the master manager, except not shown for themself|
|9||Locales||Locales, besides the master, that the user can be used to translate or review. Can be changed by the master manager|
|10||Status||Whether enabled. Can be changed by the master manager|
|11||Remove||Action to completely remove the user. Can be actioned by the user or the master manager|
Managers and writers can change their own ID, Full name, Known as and Email, but except for the master manager, the changes will not be completed until the next master manager action. Except for the master manager, they can also Remove themselves, with the same wait for the master manager.
Only the master manager can specify the user URL as not all user web sites will fit in with the ethos of the site, so may not be suitable for the tacit recommendation that making a link to it implies.