Navigation

Navigation
OIS Web Support

Email:
webhelp@
listserv.med.unc.edu

Walk-in Support:
Multimedia Lab
067 MacNider Hall
M-F 9am-4pm

Phone Support:
(919) 966-3519

You are here: Home > Overview > Site Tour > Permissions & Roles
Document Actions

Permissions & Roles

Permissions specify exactly what a user can do. A role designates a group of permissions.

Permissions

One user may be able to do “A” but not “B” in a given context.  For example, someone in the role of ‘Content Publisher’ has permission to change the state of content to private, public draft, or published, except for the case of folders.

 

Roles

Content Creator

  • Actions: Content Creators can create content (besides folders) and edit content they own as long as it exists in private or public draft state.
  • Workflow States: Content Creators can make an object private or public draft, but cannot publish an object.

Content Publisher

  • Actions: Content Publishers can create content objects (besides folders) and edit content they or content creators own, and edit (but not delete) content shared by site managers or administrators. If a creator's public draft content doesn't appear in the contents view of a folder, a publisher can see it via the direct URL to the content. Private content can't be edited unless the publisher owns it.
  • Workflow States: Content Publishers can make an object private, public draft, or published. Publishers cannot affect the state of a folder.

Site Manager

  • Actions: Site Managers can create content objects (including folders), as well as edit and delete objects they own and/or owned by content publishers and content creators, regardless of workflow state.
  • Workflow States: Site Managers can make any object public draft or published, including folders.  If ownership has been shared, site managers can make objects private, as well.

Site Administrator

  • Actions: Site Administrators can create content objects of all kinds within all sites, and edit/delete objects they own or owned by anyone else, regardless of workflow state.
  • Workflow States: Site Administrators can make any object private, public draft or published, including folders.

 

Ownership

  • Ownership is automatically attributed to the author/creator of any piece of content.
  • Ownership is characterized by the abilities to:
    • Edit content
    • Make content private
    • Delete content, if the content container's (folder's) ownership has been shared by a Site Manager
    Even so, ownership is subject to permissions that a role dictates. For instance, a content creator owns a page that they create, but once it’s published by a higher role, the creator can’t retract it from the published state, or delete it.
  • Content can have several owners. This is achieved through “sharing” ownership. Site Administrators automatically have shared ownership of all content on a site.

[top]

Site-wide Actions
Personal tools