An architect is a superuser and controls the member administration for an organisation: an architect can invite members, set-up member profile fields and specify member access levels. An architect is also able to control key settings on the platform; for example, controlling which grids different members can access, whether members can individually configure change notifications etc. The architect member class is typically assigned to methodology “Thought Leaders” within an organisation and/or to those who oversee service quality and delivery consistency. You can have multiple architects.
Thereafter, architects and builders have very similar rights. Both can create a grid, edit its name and description, add and move stages/themes and edit stage/theme names. Both can then also build-out the content of your individual grids. This is done by creating/populating individual elements with all subsidiary information and resources: descriptive text, documents and files, external links, links to other elements and expert-tags.
Builders are typically domain experts and/or service leaders/managers well-placed to keep grids constantly reviewed and refreshed: for example, by populating “best practice” work into a grid after each completed client project. You can have multiple builders.
Finally, a user is the default member class and refers to someone with view/access only privileges. Users are typically the majority member class: made up of all members of an organisation involved in the delivery of your methods and processes.