Learning Open Journal Systems 3.4

<!DOCTYPE html> <html lang="en-US"> <title>Learning Open Journal Systems 3.4 - Users and Roles</title> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <meta property="og:title" content="Learning Open Journal Systems 3.4 - Users and Roles" /> <meta property="og:site_name" content="PKP Docs"> <meta property="og:url" content="https://docs.pkp.sfu.ca/learning-ojs/en/users-and-roles.html"> <link type="text/css" href="/css/book.css" rel="stylesheet" media="all"> <script defer src="/assets/js/smooth-scroll.polyfills.min.js"></script> <script defer src="/assets/js/fontawesome.min.js"></script> <body class="body--withSidebar"> <div class="bookHeader"> <button id="sidebarControl" class="bookHeader__sidebarControl"> <span class="fa fa-bars" aria-hidden="true"></span> <span class="fa fa-times" aria-hidden="true"></span> <span class="-screenReader">Toggle Menu</span> </button> <a class="bookHeader__logo" href="/"> <img src="/img/logo-on-white.png" alt="PKP Docs" class="bookHeader__logoImage"> </a> <div class="bookHeaderTools"> <div class="search"> <style> div#___gcse_0 { display: inline-block; width: 400px; } </style> <script> (function() { var cx = '74ff67fd23b5b4a59'; var gcse = document.createElement('script'); gcse.type = 'text/javascript'; gcse.async = true; gcse.src = (document.location.protocol == 'https:' ? 'https:' : 'http:') + '//cse.google.com/cse.js?cx=' + cx; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(gcse, s); })(); </script> <gcse:searchbox-only></gcse:searchbox-only> </div> <div class="versions"> <span class="version version--current">3.4</span> <a href="/learning-ojs/3.3/" class="version">3.3</a> <a href="/learning-ojs/3.2/" class="version">3.2</a> <a href="/learning-ojs/3.1/" class="version">3.1</a> </div> </div> </div> <div class="book"> <a href="#sidebar" class="-screenReader"> Jump to table of contents </a> <div class="book__page"> <div class="book__content"> <div class="book__improve"> <a href="https://github.com/pkp/pkp-docs/edit/main/learning-ojs/en/users-and-roles.md"> Edit this page </a> or <a href="https://pkp.sfu.ca/documentation-feedback/"> make a suggestion </a> </div> <h1 id="users-and-roles"> Users and Roles </h1> <div class="book_page_toc"> <h2>Table of Contents</h2> <ul> <li><a href="#managing-users">Managing Users</a> <ul> <li><a href="#users">Users</a></li> </ul> </li> <li><a href="#permissions-and-roles">Permissions and Roles</a> <ul> <li><a href="#editing-roles">Editing Roles</a></li> <li><a href="#create-new-roles">Create New Roles</a></li> </ul> </li> <li><a href="#site-access-options">Site Access Options</a></li> </ul> </div> <p>This section provides information on accessing all of user accounts associated with your journal, as well as managing roles and permissions.</p> <h2 id="managing-users"> Managing Users <a href="#managing-users" class="book_heading_anchor" title="Link to Managing Users section">#</a> </h2> <p>This PKP School video explains how to manage users in OJS. To watch other videos in this series, visit <a href="https://www.youtube.com/playlist?list=PLg358gdRUrDVTXpuGXiMgETgnIouWoWaY">PKP’s YouTube channel</a>.</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/_AAtxnFEodQ" title="Video of how to manage users in OJS" class="youtube" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen=""></iframe> <p>In addition to managing the journal web site, the Journal Manager is also responsible for all of the user accounts in the system.</p> <p>To view the user accounts, select Users & Roles from the left menu.</p> <p><img src="/learning-ojs/en/assets/learning-ojs3.1-jm-users.png" alt="Users and Roles screen with list of journal users" /></p> <p>If you want to export a list of all registered users, you can find the option to export it as an XML file under the <strong>Tools</strong> menu. If you prefer your user data in a spreadsheet format, you can download it as a CSV file from <strong>Statistics > Users</strong>.</p> <h3 id="users"> Users <a href="#users" class="book_heading_anchor" title="Link to Users section">#</a> </h3> <p>Users are displayed in last name order.</p> <p>You can edit a user account by selecting the blue arrow to the left of an entry.</p> <p><img src="/learning-ojs/en/assets/learning-ojs3.1-jm-users-edit.png" alt="Blue arrow selected by a user's name with options to edit their account" /></p> <p>This opens the options to Email, Edit User, Disable, Remove, Login As, Merge User.</p> <h4 id="email-users"> Email Users </h4> <p>If you want to email a user about a particular submission, you can use the Discussion feature in the submission. This keeps all communication about a submission in one place.</p> <p>To send an email to a user that is unrelated to a submission:</p> <ol> <li>In the Journal Manager or Editor’s dashboard, go to Users & Roles > Users</li> <li>Find the user you want to email</li> <li>Click the blue arrow next to the user’s name to reveal links below it</li> <li>Click Email. A pop-up box will appear where you can type in your message and send it</li> </ol> <p><img src="/learning-ojs/en/assets/learning-ojs-3-users-email.png" alt="Email pop-up box for emailing a user" /></p> <h5 id="bulk-email-notifications-by-role"> Bulk Email Notifications by Role </h5> <p>In OJS 3.3 you can email multiple users at the same time using the Notify tab. This feature will need to be enabled for each journal by the journal administrator under Site Settings > Bulk Emails. The site administrator can also disable certain roles in the journal from receiving bulk emails under Hosted Journals > Settings Wizard.</p> <p>If enabled for the journal by the site administrator, emails can be sent to all users in one or more role, such as all journal managers and / or all section editors, etc. See <a href="./site-administration#site-settings">Site Administration > Site Settings</a> for instructions on enabling this feature.</p> <p>In the Notify tab, select the user roles that you would like to email. Type your subject and email message. You have the option to send a copy of the email to your own email address. You will receive a status notification indicating that the message was sent successfully.</p> <p><img src="/learning-ojs/en/assets/learning-ojs3.3-users-roles-notify.png" alt="OJS 3.3 selecting multiple users to notify with an email message" /></p> <p>This email feature can be used to send practical, core service emails to users who are actively working on the journal. For example, you might send an email to all copy editors reminding them of the “house style” for a particular word use or spelling. Avoid using this feature to notify large numbers of readers; the Announcement feature is preferable for large broadcast emails. See <a href="./settings-website#announcements">Website Settings > Setup > Announcements</a> for details about this feature.</p> <p>If several recipients flag your message as spam, it could result in all emails from the journal being sent to the spam folder. Care must be taken not to abuse this feature by sending excessive, unwanted emails. Become familiar with anti-spam and email privacy laws in your region, such as CASL in Canada and GDPR in the EU and UK. Note that there is no “unsubscribe” option available for users who receive these emails.</p> <p>It is not possible to add cc or bcc addresses other than your own, or to add attachments to messages. To send attachments you can instead use the Discussion feature or the Submission Library.</p> <p><strong>Edit User</strong> allows you to make changes to that user’s account.</p> <p><img src="/learning-ojs/en/assets/learning-ojs-3-users-edit-user.png" alt="Edit information about a user" /></p> <p><strong>Disable</strong> keeps the account in place, but blocks the user from accessing it.</p> <p><strong>Remove</strong> un-enrolls the user from all roles in the journal, but the user account remains in the system. The only way to actually remove a user account from your system is to <strong>Merge Users</strong> (see below).</p> <p><strong>Login As</strong> allows you to temporarily log in as that user, for example, to complete an outstanding task.</p> <h4 id="merge-user"> Merge User </h4> <p>The Merge User feature lets you fold this user account, including any submissions or assignments, into another user account on your system.</p> <blockquote> <p><strong>Note</strong>: This is the only way to completely delete an account from the system.</p> </blockquote> <p>You may want to create a dummy user account (e.g., Deleted Users), and use that to merge unwanted accounts into.</p> <p>To merge users:</p> <ol> <li>At Users & Roles > Users, find the user account you want to remove</li> <li>Click the blue arrow next to the username</li> <li>Click <strong>Merge User</strong> from the menu that appears below</li> <li>Find the user account that you want to merge this user account into (the user you want to maintain)</li> <li>Click the blue arrow next to username</li> <li>Click <strong>Merge into this user</strong></li> <li>Press <strong>OK</strong> to confirm</li> </ol> <h4 id="search-users"> Search Users </h4> <p>When you have a large number of users, you will want to take advantage of the search feature.</p> <p><img src="/learning-ojs/en/assets/learning-ojs-3-users-search.png" alt="Search for a journal user by name, email, and role" /></p> <p>This can help you quickly find a user by first name, last name, or email address, or to see all users in a particular role.</p> <p><strong>Note</strong>: If you leave the Search field blank, select a Role, and hit Search, you will get a list of all users in that role (e.g., all copyeditors).</p> <p><img src="/learning-ojs/en/assets/learning-ojs-3-users-search-roles.png" alt="Search for all users with a given role" /></p> <h4 id="add-user"> Add User </h4> <p>To add a new user to your journal, select the Add User link. This will open a new window with a set of fields to fill in.</p> <p><img src="/learning-ojs/en/assets/learning-ojs-3-users-add-new.png" alt="Add a user and enter their information" /></p> <p>Once these fields are completed and you hit <em>Save</em>, you will then be asked to assign roles to the new account. Use the <em>Add Role</em> link to open the role selector.</p> <p><img src="/learning-ojs/en/assets/learning-ojs-3-users-add-new-roles1.png" alt="Assign a role to a new user's account" /></p> <p>Once you have added all of the roles, hit the <strong>Save</strong> button.</p> <h4 id="register-a-user-from-another-journal"> Register a User from Another Journal </h4> <p>On multi-journal installations, an Administrator or Journal Manager can register a user from Journal A as a user on Journal B.</p> <ol> <li>Log in to Journal B as an Administrator or Journal Manager account</li> <li>Go to Users & Roles > Users</li> <li>Search for the user from Journal A that you want to register on Journal B, checking off <strong>Include users with no roles in this journal</strong></li> <li>When the user appears, click the blue arrow next to their name</li> <li>Click <strong>Edit User</strong></li> <li>Scroll down to <strong>User Roles</strong> on the Edit User box that appears.</li> <li>Check off the role that you want the user to have on Journal B</li> <li>Click <strong>Save</strong> at the end of the form</li> </ol> <h4 id="if-a-user-cant-log-in"> If a User Can’t Log In </h4> <p>If a user can’t log in to your journal site, tell them to select <strong>Forgot your password</strong> on the Login page. They will then receive a reset password link by email and will be able to reset their password.</p> <p>If the user has further issues, a Journal Manager or Editor can do the following:</p> <ol> <li>Go to Users & Roles > Users</li> <li>Find the user who can’t log in and click the blue arrow next to their name</li> <li>Click the <strong>Edit User</strong> button that appears below</li> <li>Enter a new password in the <strong>Password</strong> field, making note of what the password is</li> <li>Check off <strong>User must change password on next log in</strong></li> <li>Click <strong>Save</strong> at the end of the form</li> <li>Send the new password to the user and instruct them to log in with it</li> </ol> <p>If the user still cannot log in, their account may have been disabled. To re-enable it:</p> <ol> <li>Go to Users & Roles > Users</li> <li>Find the user who can’t log in and click the blue arrow next to their name</li> <li>Look below their name for <strong>Enable</strong> or <strong>Disable.</strong> If Disable appears, the account is already enabled. If Enable appears, click it to re-enable the account.</li> </ol> <hr /> <h2 id="permissions-and-roles"> Permissions and Roles <a href="#permissions-and-roles" class="book_heading_anchor" title="Link to Permissions and Roles section">#</a> </h2> <p>This PKP School video explains how to manage roles in OJS. To watch other videos in this series, visit <a href="https://www.youtube.com/playlist?list=PLg358gdRUrDVTXpuGXiMgETgnIouWoWaY">PKP’s YouTube channel</a>.</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/3sqD41OKuFs" title="Video of how to manage roles in OJS" class="youtube" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen=""></iframe> <p>The OJS workflow revolves around different roles with different permissions and responsibilities for each user, allowing them access to different parts of the workflow. Users in the system must have at least one role. Users can also have more than one role, for example, being a Journal Manager, Editor, and Author in the same journal.</p> <p>Each role is first assigned a permission level, which will broadly define what level of access a user has to a particular journal. Roles are then further customized by providing a position name, and granting or restricting access to various stages of the Editorial Workflow.</p> <p>There are a number of predefined roles that you can use and edit in OJS. Read in-depth about these predefined roles organized by their permissions level. Italicized roles are new in OJS 3.</p> <ul> <li> <p>The <strong>Site Administrator</strong> is a single user responsible for administration of the entire OJS installation. This permissions level will not appear in user lists or in role settings. Site administrators, by default, have access to all journals within a given instance and can take any actions that can be undertaken by Journal Managers.</p> </li> <li><strong>Journal Managers</strong> have access to the entire Editorial Workflow, as well as all other journal settings. Available predefined Journal Manager roles: Journal Manager, Journal Editor (formerly “Editor” in OJS 2), Production Manager</li> <li><strong>Section Editors</strong> have access to the entire Editorial Workflow, but cannot make any changes to journal settings. Available predefined Section Editor roles: Section Editor, <em>Guest Editor</em></li> <li><strong>Assistants</strong> can access only the parts of the Editorial Workflow assigned to their role. Available predefined Assistant roles and their assigned editorial workflow stages: <ul> <li>Submission & Review stages: <em>Funding coordinator</em></li> <li>Copyediting stage: Copyeditor, <em>Marketing and sales coordinator</em></li> <li>Production Stage: <em>Designer</em>, <em>Indexer</em>, Layout Editor, Proofreader</li> </ul> </li> <li><strong>Reviewers</strong> are users who appear when you’re assigning reviews in the Editorial Workflow and have access to that stage when they’re assigned.</li> <li><strong>Authors</strong> can make new submissions.</li> <li><strong>Readers</strong> can access the reader-facing website. This is the minimum permissions level granted to all users.</li> <li><strong>Subscription Managers</strong> can edit site access settings as well as settings related to subscriptions. This is a new permissions level in OJS 3, with one predefined role, <em>Subscription Manager</em>.</li> </ul> <p>Predefined and custom roles can be checked from the Roles tab.</p> <p><img src="/learning-ojs/en/assets/learning-ojs3.1-jm-users-roles.png" alt="Roles tab showing all current roles in the journal" /></p> <p>From this page, you can see each role, and the editorial stage each role can access. A good example of this is the Copyeditor role, which can only access the copyediting stage. Copyeditors cannot jump to the Review stage to see what happened during the peer review process. See the Editorial Workflow chapter for more information about the different editorial stages.</p> <p>In addition to assigning and editing the predefined roles, Site Administrators and Journal Managers can also create new roles or rename existing ones.</p> <h3 id="editing-roles"> Editing Roles <a href="#editing-roles" class="book_heading_anchor" title="Link to Editing Roles section">#</a> </h3> <p>Unchecking a box removes access to that stage for users with that role.</p> <p>Selecting the blue arrow to the left of the role name reveals the edit link. Clicking this opens the editing window.</p> <p><img src="/learning-ojs/en/assets/learning-ojs3.1-jm-users-roles-edit.png" alt="Edit details of a role" /></p> <p><strong>Permission Level</strong>: This indicates how much a user with this role can do in any stage.</p> <p>The Journal Assistant level can communicate with other users and upload and revise files. In Journals where only one user has been assigned with an Assistant role, they will be automatically assigned to a new submission. Once a second person has been assigned this role, this action will stop.</p> <p><strong>Role Name</strong>: You can use this field to easily rename any role.</p> <p><strong>Abbreviation</strong>: Each role must have a unique abbreviation.</p> <p><strong>Stage Assignment</strong>: This allows you to determine which stage users with this role can access.</p> <p><strong>Role Options</strong>: Use these checkboxes to show anyone with this role in the contributor list (e.g., the author list). As of OJS 3.2, roles can be assigned permission to edit submission metadata by enabling the checkbox.</p> <p>Use the second option to determine whether users can self-register in this role. Authors and Reviewers are good candidates for self-registration. You would definitely NOT want to allow users to self-register as Journal Managers or Editors!</p> <p>The third option is useful for guest editors or possibly section editors, depending upon your preferred workflow and authority chain.</p> <h3 id="create-new-roles"> Create New Roles <a href="#create-new-roles" class="book_heading_anchor" title="Link to Create New Roles section">#</a> </h3> <p>Use the <em>Create New Roles</em> link to open a window where you can create a new role for your journal, including setting which stages it can access and how much permission it should have.</p> <hr /> <h2 id="site-access-options"> Site Access Options <a href="#site-access-options" class="book_heading_anchor" title="Link to Site Access Options section">#</a> </h2> <p>This PKP School video explains how to configure site options in OJS. To watch other videos in this series, visit <a href="https://www.youtube.com/playlist?list=PLg358gdRUrDVTXpuGXiMgETgnIouWoWaY">PKP’s YouTube channel</a>.</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/lqf4GmA01PA" title="Video of how to configure site access options in OJS" class="youtube" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen=""></iframe> <p>This page allows you to determine how readers can access your journal.</p> <p><img src="/learning-ojs/en/assets/learning-ojs3.1-jm-users-siteoptions.png" alt="Site access options tab under Users and Roles" /></p> <p><strong>Additional Site and Article Access Restrictions</strong>: Choose from these options to limit access.</p> <blockquote> <p>Keep in mind that while requiring registration to read open access content can be convenient for your tracking, it can dissuade some people from reading your content. Use with care.</p> </blockquote> <p><strong>User Registration</strong>: This option allows you to determine whether users can create their own accounts or must be enrolled by a Journal Manager.</p> <blockquote> <p>Allowing users to register themselves, but only into Author, Reviewer, or Reader roles, is a good choice.</p> </blockquote> <div class="book__footer"> <div class="book__improve"> <a href="https://github.com/pkp/pkp-docs/edit/main/learning-ojs/en/users-and-roles.md"> Edit this page </a> or <a href="https://pkp.sfu.ca/documentation-feedback/"> make a suggestion </a> </div> </div> </div> </div> <div class="book__sidebarScreen"></div> <div id="sidebar" class="book__sidebar"> <div class="book__summary"> <h1 id="summary">Summary</h1> <ul> <li><a href=".">Preface</a></li> <li><a href="./about-ojs">About Open Journal Systems</a> <ul> <li><a href="./about-ojs#background">Background</a></li> <li><a href="./about-ojs#ojs-features">OJS Features</a></li> <li><a href="./about-ojs#install-and-upgrade">Install and Upgrade</a></li> <li><a href="./about-ojs#whats-new">What’s New in 3.4</a></li> <li><a href="./about-ojs#community-contributions">Community Contributions</a></li> <li><a href="./about-ojs#support">Support</a></li> </ul> </li> <li><a href="./site-administration">Site Administration</a> <ul> <li><a href="./site-administration#site-management">Site Management</a></li> <li><a href="./site-administration#administrative-functions">Administrative Functions</a></li> </ul> </li> <li><a href="./journal-setup">Journal Settings</a> <ul> <li><a href="./journal-setup#masthead">Masthead</a></li> <li><a href="./journal-setup#contact">Contact</a></li> <li><a href="./journal-setup#sections">Sections</a></li> <li><a href="./journal-setup#categories">Categories</a></li> </ul> </li> <li><a href="./settings-website">Website Settings</a> <ul> <li><a href="./settings-website#appearance">Appearance</a></li> <li><a href="./settings-website#setup-1">Setup</a></li> <li><a href="./settings-website#plugins">Plugins</a></li> <li><a href="./settings-website#static-pages">Static Pages</a></li> </ul> </li> <li><a href="./settings-workflow">Workflow Settings</a> <ul> <li><a href="./settings-workflow#submission">Submission</a></li> <li><a href="./settings-workflow#review">Review</a></li> <li><a href="./settings-workflow#publisher-library">Publisher Library</a></li> <li><a href="./settings-workflow#emails">Emails</a></li> </ul> </li> <li><a href="./settings-distribution">Distribution Settings</a> <ul> <li><a href="./settings-distribution#license">License</a></li> <li><a href="./settings-distribution#search-indexing">Search Indexing</a></li> <li><a href="./settings-distribution#payments">Payments</a></li> <li><a href="./settings-distribution#access">Access</a></li> <li><a href="./settings-distribution#archiving">Archiving</a></li> </ul> </li> <li><a href="./users-and-roles">Users and Roles</a> <ul> <li><a href="./users-and-roles#managing-users">Managing Users</a></li> <li><a href="./users-and-roles#permissions-and-roles">Permissions and Roles</a></li> <li><a href="./users-and-roles#site-access-options">Site Access Options</a></li> </ul> </li> <li><a href="./statistics">Statistics</a> <ul> <li><a href="./statistics#definitions">Definitions</a></li> <li><a href="./statistics#articles">Articles</a></li> <li><a href="./statistics#geographical-and-institutional-statistics">Geographical and Institutional Statistics</a></li> <li><a href="./statistics#editorial-activity">Editorial Activity</a></li> <li><a href="./statistics#users">Users</a></li> <li><a href="statistics#reports">Reports</a></li> </ul> </li> <li><a href="./tools">Tools</a> <ul> <li><a href="./tools#importexport">Import & Export</a></li> <li><a href="./tools#permissions">Permissions</a></li> </ul> </li> <li><a href="./subscriptions">Subscriptions</a> <ul> <li><a href="./subscriptions#subscription-policies">Subscription Policies</a></li> <li><a href="./subscriptions#subscription-types">Subscription Types</a></li> <li><a href="./subscriptions#payment-types">Payment Types</a></li> <li><a href="./subscriptions#payments">Payments</a></li> <li><a href="./subscriptions#individual-subscriptions">Individual Subscriptions</a></li> <li><a href="./subscriptions#institutional-subscriptions">Institutional Subscriptions</a></li> <li><a href="./subscriptions#payment-notifications">Payment Notifications</a></li> <li><a href="./subscriptions#subscription-block">Subscription Block</a></li> <li><a href="./subscriptions#setting-articles-as-open-access">Setting Articles as Open Access</a></li> </ul> </li> <li><a href="./user-accounts">User Account Management</a> <ul> <li><a href="./user-accounts#registering-with-a-journal">Registering with a Journal</a></li> <li><a href="./user-accounts#viewing-and-changing-your-profile">Viewing and Changing your Profile</a></li> <li><a href="./user-accounts#resetting-your-password">Resetting your Password</a></li> </ul> </li> <li><a href="./authoring">Authoring</a> <ul> <li><a href="./authoring#register">Registering with the Journal</a></li> <li><a href="./authoring#submit">Making a Submission</a></li> <li><a href="./authoring#edit">Editing Submission Information</a></li> <li><a href="./authoring#respond-review">Responding to Requests for Revision or Resubmission After a Review</a></li> <li><a href="./authoring#respond-copyediting-proofreading">Responding to a Copyediting or Proofreading Request</a></li> </ul> </li> <li><a href="./reviewing">Reviewing</a></li> <li><a href="./editorial-workflow">Editorial Workflow</a> <ul> <li><a href="./editorial-workflow#tasks">Tasks</a></li> <li><a href="./editorial-workflow#submission-notifications">Submission Notifications</a></li> <li><a href="./editorial-workflow#submission-dashboard">Submission Dashboard</a></li> <li><a href="./editorial-workflow#review">Review</a></li> <li><a href="./editorial-workflow#copyediting">Copyediting</a></li> </ul> </li> <li><a href="./production-publication">Production and Publication</a> <ul> <li><a href="./production-publication#publication-tabs">Publication Tabs</a></li> <li><a href="./production-publication#format-article-for-publication">Format Article for Publication</a></li> <li><a href="./production-publication#finalize-metadata">Finalize Metadata</a></li> <li><a href="./production-publication#create-issue">Create Issue</a></li> <li><a href="./production-publication#add-the-article-to-an-issue">Add the Article to an Issue</a></li> <li><a href="./production-publication#schedule-for-publication">Schedule for Publication</a></li> <li><a href="./production-publication#versioning-of-articles">Versioning of Articles</a></li> <li><a href="./production-publication#continuous-publishing--early-view">Continuous Publishing and Early View</a></li> </ul> </li> </ul> </div> <div class="book__backToHub"> <span class="fa fa-long-arrow-alt-left" aria-hidden="true"></span> <p>Back to <a href="/">all documentation</a>.</p> </div> <div class="book__spacer"></div> </div> </div> <div class="book__footerWrapper"> <div class="siteFooter"> <nav class="siteFooter__container"> <div class="siteFooter__top"> <div class="siteFooter__nav"> <div class="siteFooter__navHeader"> Contact Us </div> <p>Have a question or suggestion about PKP’s documentation and user guides? <a href="https://pkp.sfu.ca/documentation-feedback/">Use our documentation contact form</a>.</p> <p>If your message is not about documentation, please use the general <a href="https://pkp.sfu.ca/contact-us/">contact form</a>.</p> </div> <div class="siteFooter__nav"> <div class="siteFooter__navHeader"> Community </div> <p><a href="https://pkp.sfu.ca/documentation-interest-group/">Documentation Interest Group</a></p> <p><a href="/contributing/en/">Contributing Documentation</a></p> <p><a href="/translating-guide/">Translating Guide</a></p> <p><a href="https://forum.pkp.sfu.ca">Community Forum</a></p> </div> <div class="siteFooter__nav"> <div class="siteFooter__navHeader"> About </div> <p><a href="https://pkp.sfu.ca">Public Knowledge Project</a></p> <p><a href="https://pkpservices.sfu.ca/">PKP|Publishing Services</a></p> </div> <div class="siteFooter__logo"> <a href="https://pkp.sfu.ca"> <img src="/img/logo-on-grey.png" alt="Public Knowledge Project"> </a> <p>The Public Knowledge Project is a Core Facility of Simon Fraser University</p> <p>888 University Drive, Burnaby, B.C., Canada V5A 1S6</p> <p>We respectfully acknowledge that SFU occupies the unceded traditional territories of the Coast Salish peoples of the Musqueam, Squamish, and Tsleil-Waututh Nations.</p> </div> </div> <div class="siteFooter__bottom"> <p class="footer-copyright"><span class="terms-text"><a href="https://www.sfu.ca/contact/terms-conditions.html" target="_blank">TERMS & CONDITIONS</a> © SIMON FRASER UNIVERSITY.</span><span class="copyright-text"><img src="/img/creativecommons.svg" alt="Creative Commons logo" /><img src="/img/attribution.svg" alt="Attribution icon" /><a href="https://creativecommons.org/licenses/by/2.0/" target="_blank">CC-BY 2.0</a></span><span class="footer-copyright-separator"> | </span><span class="ab-link">Website by <a target="_blank" href="https://www.affinitybridge.com">Affinity Bridge</a></span></p> </div> </div> </div> </div> <script type="text/javascript">/** * Toggle the sidebar open/closed */ (function() { var sidebar = document.getElementById('sidebar'); var sidebarControl = document.getElementById('sidebarControl'); var isOpen = false; var sidebarOpenClass = ' -sidebarIsOpen'; if (!sidebar || !sidebarControl) { return; } // Toggle sidebar function toggle() { if (isOpen) { document.body.className = document.body.className.replace(new RegExp(sidebarOpenClass, 'g'), ''); } else { document.body.className = document.body.className + sidebarOpenClass; } isOpen = !isOpen; } sidebarControl.addEventListener('click', toggle); })(); </script> <script type="text/javascript">/** * Initialize smooth scrolling to anchor links * * See: https://github.com/cferdinandi/smooth-scroll */ (function() { function init() { if (typeof SmoothScroll === 'undefined') { setTimeout(init, 500); } else { var scroll = new SmoothScroll('a[href*="#"]', {easing: 'easeInOutCubic', offset:80}); } } init(); })(); </script>  <script async src="https://www.googletagmanager.com/gtag/js?id=UA-130558797-1"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-130558797-1'); </script>  <script> (function(h,o,t,j,a,r){ h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)}; h._hjSettings={hjid:2436159,hjsv:6}; a=o.getElementsByTagName('head')[0]; r=o.createElement('script');r.async=1; r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv; a.appendChild(r); })(window,document,'https://static.hotjar.com/c/hotjar-','.js?sv='); </script>  <script type="text/javascript"> var _paq = _paq || []; _paq.push(["setDocumentTitle", document.domain + "/" + document.title]); _paq.push(["setCookieDomain", "*.docs.pkp.sfu.ca"]); _paq.push(["setDomains", ["*.docs.pkp.sfu.ca"]]); _paq.push(["trackPageView"]); _paq.push(["enableLinkTracking"]); (function() { var u = (("https:" == document.location.protocol) ? "https" : "http") + "://" + "matomo.publicknowledgeproject.org/pkp/"; _paq.push(["setTrackerUrl", u + "piwik.php"]); _paq.push(["setSiteId", "40"]); var d = document, g = d.createElement("script"), s = d.getElementsByTagName("script")[0]; g.type = "text/javascript"; g.defer = true; g.async = true; g.src = u + "piwik.js"; s.parentNode.insertBefore(g, s); })(); </script>  </body> </html>

CINXE.COM

Learning Open Journal Systems 3.4 - Users and Roles