Responsibilities & Access

There are a few different types of access accounts that exist within the CMS. This is for governance purposes and adhering to policies that DNSW needs to comply with. Publishers = Digital Content Team members who are responsible for managing, maintaining and running the consumer website content for Sydney.com & Visitnsw.com. They can publish and/or archive. Editors = Users given training who are outside the Digital Content Team and are responsible for making editorial copy changes to existing content in the consumer websites Sydney.com & Visitnsw.com. They cannot publish. Approvers = Users with authority to approve content in the consumer websites Sydney.com & Visitnsw.com who do not need access to make direct changes in the CMS. Access is given to view unpublished content in 'draft mode'. Publisher Access These users can: create/build content, widgets, pages, articles edit existing content, widgets, pages, articles upload images & videos publish and archive all content approve or reject with notes content changes sent from editor accounts These users cannot: change the functionality of the website change the physical specs of the website such as padding (white space), header specs, fonts, button shape etc Editor Access These users can: edit existing content such as editorial copy edit existing image captions send all content edits for approval to publisher account These users cannot: publish or archive any content - it will always be sent for approval to the Publisher Accounts Approval Account These users can: view unpublished content in the CMS to provide feedback via Monday.com interact with unpublished content such as urls/images/videos & ensure they approve user journey These users cannot: build/edit/archive/publish any content

User Account Creation

No matter what level of access, if a new account is needed to be created in Drupal, you will need to log a ticket in Jira for the developers to action. Make sure you specify what level of access is needed. Currently, the Project in Jira is still "Drupal 8" (even though we are up to Drupal 10) and the issue type select "Task". An example of what would be submitted in Jira on a ticket is (pick from the list of relevant platforms): Publisher account Hello, Can we please set up Millie Harvey before Monday the 21st November for the following? Access level is Publisher. Email/user: millie.harvey@dnsw.com.au Jira Sydney.com Visitnsw.com Slack If it just for an editor account , you will only need the following: Hello, Can we please set up Millie Harvey before Monday the 21st November for the following? Access level is Editor. Email/user: millie.harvey@dnsw.com.au Sydney.com Visitnsw.com

All User Login Details

No matter what your level of access is everyone has the same place to log into the CMS All users now log into Visitnsw first, which then allows you to access Sydney. Meaning if you log into VisitNSW, you are automatically logged into Sydney Urls are: Sydney: https://www.sydney.com/user/login Visitnsw: https://www.visitnsw.com/user/login For logging into the international sites please view the whole section on this Digital Publisher Guide page, titled: "Program/Platform Links"

"For Review" - The content team's QA approval process

If you are a Publisher and therefore have the delegation of approving content sent to you for review (either copy changes or widget/template changes) you can access all pending changes here: https://www.sydney.com/admin/content/for-review https://www.visitnsw.com/admin/content/for-review Note: it is located once logged into the CMS under Content > For Review (1st option on menu)