Skip to main content
Ontario Tech acknowledges the lands and people of the Mississaugas of Scugog Island First Nation.

We are thankful to be welcome on these lands in friendship. The lands we are situated on are covered by the Williams Treaties and are the traditional territory of the Mississaugas, a branch of the greater Anishinaabeg Nation, including Algonquin, Ojibway, Odawa and Pottawatomi. These lands remain home to many Indigenous nations and peoples.

We acknowledge this land out of respect for the Indigenous nations who have cared for Turtle Island, also called North America, from before the arrival of settler peoples until this day. Most importantly, we acknowledge that the history of these lands has been tainted by poor treatment and a lack of friendship with the First Nations who call them home.

This history is something we are all affected by because we are all treaty people in Canada. We all have a shared history to reflect on, and each of us is affected by this history in different ways. Our past defines our present, but if we move forward as friends and allies, then it does not have to define our future.

Learn more about Indigenous Education and Cultural Services

CMS user roles

Departments and faculties who manage their own website content typically have multiple users trained to edit content in the CMS. Different user roles are assigned to specific users. Workflows on each site enable an approval process for pages and content to ensure accuracy, professionalism and consistency.

There are four types of user roles in the CMS.

Summary of workflow steps. Description of each role is below.

Contributor – can create and edit pages, but cannot publish pages directly to the live website (a workflow must be initiated). When a contributor creates or edits a page, it is sent to the Approvers.

Approver – can create and edit pages, but cannot publish pages directly to the live website (a workflow must be initiated or continued). Approvers can also approve or send back content that contributors have created. When an approver creates, edits, or approves a page, it is sent to the Publishers. 

Publisher – can create and edit pages, and can publish pages directly to the live website (can bypass the workflow). Publishers can also approve and publish or send back content that approvers have created or approved. When a publisher approves a page, it is published to the live website. If there is a technical issue with the page, a publisher can send the page to the Administrators.

Administrator – can create and edit pages, and can publish pages directly to the live website (can bypass the workflow). Administrators typically do not receive workflow pages unless there is a technical issue with the page.

Administrators are Communications and Marketing Web Team developers. Publishers are typically Communications and Marketing Communications Officers. Most users will be in a contributor or approver role.

User roles are assigned for each faculty/department group (if a faculty or department manages multiple sites) or for individual websites. There can be multiple users assigned to a role. On some sites where there are fewer editors, the approver role can be removed so that the workflow process is condensed from contributor to publisher to Web Team. 

Search the CMS User Guide