Documentation

RingMaster collaboration

There are three general types of workflows supported by RingMaster

One Tier

A one person shop, the webmaster writes all the HTML, builds and maintains the site. There are a lot of small to medium websites produced in this type of environment

Two Tier

There is a webmaster who deals with running the server, determining the layout of HTML. The webmaster is responsible for assembling and managing the site. There are a number of authors who are responsible for creating content, and they work with the webmaster to integrate their content into the website.

Three Tier

The webmaster is again responsible for building and structuring the site in coordination with designers. But between the webmaster and authors is a tier of editors. Editors are responsible for overseeing various parts of the website, and for insuring that the content is up to standards and produced on time.

• SuperUser - has full access to the RingMaster system and all objects
• Owner - has complete control over the objects designated as owned by that user
• User - Has limited control over objects assigned to. Level of control is determined by the owner or superuser. Any changes made to objects by users must be approved by the owner or super user.

Before being assigned to any role a person must first be set up as a registered RingMaster User.

Roles:

SuperUser

The superuser has complete access to the RingMaster system. Anyone using RingMaster from the Frontier interface instead of through the web is considered to be the superuser. This person has the ability to create and manage users, has complete access to any project, determines owners and their access rights, and can act as a librarian for any file checked out through RingMaster's custody system. The superuser can be defined as a group if more than one person needs this level of access.

Owner

Owners and users are defined for individual regions of a project as a property of an object (either folder or file). They are part of the collaboration property set. The specific access of each role is set in the access property set. These access permissions determine what the person may actually do, can they delete something - rename it, check it out etc. The access rights for an owner are set by the superUser. The files or folders assigned to a owner or user is said to be that persons domain. Depending on the permissions of the owner as set by the superuser, the owner may then be able to set who is a user of particular objects within their domain, and those users access rights.

User

A user is similar to an owner but who can not assign anyone to work on any part of a project that is within their domain. The access rights of a user are set by the superuser or by the owner of the domain they are working within.

Groups

In addition to assigning an individual user to a domain, you can also assign a group as an owner. This gives a collection of people equal access by putting them all in the same role. For "Users and Groups" for more information about groups.

Table of Contents -- Prev -- Next