6 Users

Depending upon their role, users have varying degrees of access to the site.

Smallsite Design sites are designed for being public displays of information. Users do not have any exclusive services available for them, but are purely for creating content and administrative tasks. Most sites will have only one manager and occasional writers for reviewing. Multi-lingual sites will have writers for translating.

The four user roles are:
#	Role	Activities
1	Manager	Site owner or 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	Contributor	A phantom placeholder for a manager or writer who has been removed but there are still articles that they have contributed to still needing their name
4	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

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 a relative, friend or acquaintance that can do a bit of writing or web programming, but whom you would not trust with your bank account, is unlikely to be a good manager.

There can be multiple managers, only one of which can be the master manager at any one time. 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 30 minute timeout has elapsed. This allows running the master manager role in shifts, if the site is managed in a busy scenario that needs it.

The writer role is suitable for contractors, by providing access only for writing, translating, editing or reviewing a particular article, or articles that can be used as a source for it. However, any manager can also be assigned any article body task. While managers and writers can be assigned any such task for the master locale, other locales must be enabled for them. The rationale for this is that all users should be familiar with the master locale's language and script, but they need to have proficiency in other locales to have be assigned tasks for them.

Even though a manager or writer may have been removed from the site, any articles they have contributed to still need to have an attribution for the tasks they have performed as part of their moral rights. Those roles are converted to the contributor role as a placeholder for the name used in the Contributors block in article footers. If not wanting attribution any more, change Full name to Anonymous (or equivalent for the master locale) before deleting the user account, or get the master manager to modify it in the contributor record.

Guest roles are not for a real person, but a role that allows multi-person access with a common Password for viewing almost all the pages of a demonstration or learning site, including management pages, but have no ability to change anything. Guests cannot see the Email nor URL field contents for other users. Typically, such sites would have a single token manager user, with bogus details, for setting up and managing the site.

Guests can only be created if the site is in Guest mode as enabled in the Access section of the Settings page. Changing a site out of guest mode will delete all guest accounts. When a guest account is reset, the master manager receives an email with a generated password. They can then provide that and the user ID to individuals or a group so they can have access to a site that is only for them.

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 value element. This allows for a site to be publicly accessed for demonstration purposes by multiple people using the same login.

Details

△

All users have the same basic details.

The user details fields are:
#	Name	Description
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	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 only be changed by the master manager
6	Accessibility	Personal accessibility setting for the user when using management pages. Can only be changed by the user
7	Show hover	Personal setting for whether all the semi-transparent squares indicating the positions of hover buttons are displayed in the Article body page. Can only be changed by the user
8	Expiry	Date user will be disabled. New writers have an expiry of a month. Master manager can extend by set periods. Never shown for managers as they never expire
9	Role	Current role. Can be changed for other users by the master manager, and only between manager and writer roles. Not shown for the master manager
10	Locales	Non-master locales that the user can be assigned to translate, edit or review. All users can be assigned phases for the master locale. Can be changed by the master manager
11	Status	Whether enabled. Can be changed by the master manager, except for themself
12	Remove	Action to remove the user. Can be actioned by the user or the master manager on their behalf. Not shown for 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 upon the master manager.

Any names used in the Contributors field will not be affected if a user of that Full name is removed, as those users are converted to contributor roles so they can continue to supply their name so that their moral rights to attribution for the tasks they performed are retained. However, a master manager can change them. The Contibutors field is updated when an article is released and is automatically created from the phase records. The three tasks listed are Write, Translate and Review, along with the locale worked upon.

Any users that are currently not a contributor to any article have an * after their ID in the section's navigation bar, and a light orange background to the first cell in their table row. At least once a day when a master manager logs in, if there are no more articles for which they performed tasks, contributors are automatically removed, but can also be manually removed before then.

If the name in a Contributors field matches a user's Full name and they have a URL specified, their name will be a link to the URL. Only the master manager can specify the user URL as not all users' 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. When a manager or writer is removed and converted to a contributor role, their URL along with most other details are removed, with the Full name field one of the few that remain and the only one that is editable.

If not wanting attribution any more, change Full name to Anonymous (or equivalent for the master locale) before deleting the user account, or get the master manager to modify it in the contributor record.

A Reset button is shown after a user's ID so that the master manager can reset their password if they forgot it. An email is sent to their Email address with a temporary password, which is valid for only eight minutes to limit the risk of it being used by anyone else. The button is only shown to the master manager, but not for themselves. Any user can create a new password for themselves at the Password item in the Other section of the Work list page.

Consolidating documents

△

When building a new document from content from others, extra steps are required to ensure all the contributors to the content used are included.

For sites with more organic growth of articles, over time there might be opportunities to amalgamate content from many articles to give them a more organised structure. If creating a new blank article for this, the person building it from content from other articles will be the only contributor listed. This present no issues if they wrote the other source articles, but if there are many contributors across all the source articles, clone the source article that has the most of the relevant contributors, then edit it to delete unwanted content and add from the other source articles.

For any contributors to any of the source documents who are still a user, to include them in the list, assign a task to them but have them immediately make a draft and click the ending phase button (such as Written if assigned Write) without adding any content.

For users who no longer exist on the site, add a user with the same ID, Full name and locales. Assign a relevant task to them, log in as them and immediately make a draft and click the ending phase button. Remove that user to convert them to a contributor. From then on, they can be assigned a task which will automatically generate the ending task, bypassing having to log in as them again.