Associations are a combination of a users, groups, roles and weblogs which, together, afford some set of weblog-level capabilities within the system.
Associations can be created in four different ways:
Creating an association in the first way is a three-step process (Select user/group, role, weblog). In the latter three cases, it's a two step process since one desired element is already in context. While system administrators can create and manage associations for any weblog, with Movable Type Enterprise v1.5, weblog administrators can create and manage associations for the blogs which they administer.
Note: Only System Administrators can create associations.
See also: Managing User and Group Permissions
Permissions are now part of Roles, but the order in which the Permissions are displayed in the Role Details have been re-ordered so as to show importance of the permissions:
See also: Roles
Movable Type Enterprise has a granular permission system which allows administrators to finely control what each user is allowed to do within the system. To accommodate this the following entities are used:
The high-level profile that is defined by default within Movable Type Enterprise is System Administrator. All lower level permission profiles contain a combination of permissions assigned through the roles and associations.
Unique combinations of user privileges comprise various permissions profiles. It is up to your organization to define these assignments and the privileges of which they are comprised, as well as assign permissions to the right individuals for use with the right weblogs.
System Administrators have no restrictions within the system and inherit all privileges for all weblogs within that system, regardless of their specific association with a particular weblog. Responsibilities include, but are not limited to:
Permissions are defined through the groups and associations assigned to the user.
To see what permissions are associated with your username
To view and modify permissions for other users
Note: The following procedure requires System Administrator permission.
To associate a user with a new or additional weblog
Note: The following procedure requires System Administrator permission.
View the groups and associations assigned to the user. Edit the associations and roles assigned to the user.
Roles allow administrators to map real-world labels onto sets of permissions like, Designer or Writer allowing for almost natural language assignment in the form of a rule, called an Association.
While a single user or group can have any number of roles on a particular weblog, it is best practice to create broad roles which encompass all of the desired permissions so that each user/group has only a single role (or two maximum) on each weblog. This will greatly reduce your management burden in the future.
Default Roles
The system ships with a number of default roles which cover a number of popular personas and capabilities. These default roles are not special in any way. They are completely customizable in both name, description and permissions and can be deleted if the administrator finds them unsuitable. New roles can also be created in place of or in addition to the default roles.
Each of these roles can be modified or even deleted. Other roles can be created to better match your workflow and job descriptions.
Custom Roles When Upgrading
Upon upgrade, the system maps each users' sets of permissions to each default role and if a match is found, the default role is granted in place of the individual permissions. When the permission sets don't match up, a Custom role is created for them, system-wide and each user with that set of permissions on any weblog will be granted that Custom role.
After upgrade, these Custom roles can be edited, properly named to describe the persona or combined manually with the default roles. For best results, we recommend that all Custom roles are at least renamed making it easier to differentiate between each.
See also: Associations