{"id":9599,"date":"2018-01-19T13:16:57","date_gmt":"2018-01-19T13:16:57","guid":{"rendered":"https:\/\/kb.sambapos.com\/?p=9599"},"modified":"2018-04-10T11:37:06","modified_gmt":"2018-04-10T11:37:06","slug":"2-2-10-a-how-to-create-change-user-roles","status":"publish","type":"post","link":"https:\/\/kb.sambapos.com\/en\/2-2-10-a-how-to-create-change-user-roles\/","title":{"rendered":"2.2.10.a. How to Create \/ Change User Roles?"},"content":{"rendered":"

User roles are used to organise, limit and determine the roles and authoritiy of users. User can only see and perform process on the screens that related to own task area. User can not display and perform process on the screens that out of role.<\/p>\n

There are three stages for creation of authorization groups. Firstly prepare the roles by paying attention of user’s duties and responsibilities in the restaurant. When you adding the users, this will be assigned to Role \/ Authority groups.<\/p>\n

    \n
  1. Program Role – Authorizations<\/li>\n
  2. User Administration Section Authorizations<\/li>\n
  3. User Association Authorizations<\/li>\n<\/ol>\n

    1. Program Role – Authorizations\u00a0<\/span><\/h2>\n

    Manage > Users > Roles > Authorizations<\/strong> from here by adding a new role, type the role name. Create Role Authorization Groups by clicking on titles which listed on Roles Section. Create basic role authorization groups like in the example below. You can create or edit new Role-Authorization Groups by customizing according to groups or users.<\/p>\n

    Sample Role Authorization Groups Names;<\/strong><\/p>\n

    Admin
    \nManager
    \nCashier
    \nWaiter<\/p>\n

    \"\"<\/p>\n

    Click and activate the small box which will be authorized. You can make changes about these authorizations by editing roles later on.<\/span><\/p>\n

    \"\"<\/p>\n

    Navigation Permissions<\/strong><\/span><\/h3>\n

    Navigation is the main screen which is displayed by entering admin password. On the navigation screen as default; Work Periods, POS, Tickets, Accounts, Warehouses, Samba Market, Reports, Manage and Logout titles are exist.<\/p>\n

    Authority Titles<\/span><\/h4>\n
      \n
    • Can Restore Fullscreen: <\/strong>It gives permisson to zoom in or out for screen window.<\/li>\n
    • Can Display Account Screen: <\/strong>On the navigation screen the place that income and expense information\u00a0 and entity account’s displaying authorization.<\/li>\n
    • Can Approve Admin Pin: <\/strong>The authorization that on the previously determined Automation Commands requiring Admin Pin approval. For example; Admin Password Necessity can be used for automation commands such as Void, Gift, Lost.<\/li>\n
    • Can Navigate Warehouses: <\/strong>Accessing\u00a0 to Warehouses on navigation screen can be authorized.<\/li>\n
    • Can Open Management: <\/strong>On the navigation screen this authorization gives permission to access program setup, settings and editings.<\/li>\n
    • Can Navigate Market: <\/strong>On the Navigation Screen accessing Market section can be authorized.<\/li>\n
    • Can Enter Navigation Screen: <\/strong>Displaying authorization of entering main screen after typing SambaPOS Entry password.<\/li>\n
    • Can Start End of Day: <\/strong>Entry authorization of Work Periods on the Navigation Screen.<\/li>\n
    • Can Display Reports: <\/strong>Access authorization for Reports on the Navigation Screen.<\/li>\n<\/ul>\n

      Account Permissions<\/strong><\/h2>\n
        \n
      • Can Create Account: <\/strong>Creating account authorization for debiting and crediting of Entities (Customers, Members).<\/li>\n<\/ul>\n

        Ticket Permissions<\/strong><\/h2>\n

        Activate by selecting the titles that entity, ticket and order authorizations are edited.<\/p>\n

        Authorization Titles<\/strong><\/span><\/h2>\n
          \n
        • Can Remove Ticket Lock:<\/strong> Determines locking or pausing of document processes.<\/li>\n
        • Can Remove Ticket Tag: <\/strong>Authorization of removing ticket tag.<\/li>\n
        • Can Merge Tickets:\u00a0<\/strong>For the same document types, combining authorization of more than one documents with their contents and accounts into a single document.<\/li>\n
        • Can Display Old Tickets: <\/strong>Authorization to see the tickets title on the navigation screen.<\/li>\n
        • Can Update Extra Modifiers:
          \n<\/strong><\/li>\n
        • Can Display Other Waiters Tickets: <\/strong>The users who are in the same role \/ authorization group can continue processes on ticket that they took orders. Only the user who first took the order into ticket can see and perform process, other users can not.\u00a0(The user who has Admin authorization can see and perform process.)<\/li>\n
        • Can Remove Entity From Ticket:\u00a0<\/strong>If it is selected, user can change or remove the entity, if it is not selected, user can’t change the entity.<\/li>\n
        • Can Change Order Quantity: <\/strong>Authorization for using the (+ – ) buttons to increase or decrease order quantity when taking order.<\/li>\n
        • Change Selected Order Quantity: <\/strong>Authorization of using (+ – )\u00a0 buttons on the ticket quantity selection of taken orders.<\/li>\n
        • Can Change Ticket Entity:<\/strong>\u00a0If it’s selected user can change or move\u00a0ticket entity. ( Table, Customer )<\/li>\n<\/ul>\n

          Reporting Permissions<\/strong><\/h2>\n
            \n
          • Can Change Report Date Filter:\u00a0 <\/strong>In the reports section, user can display the reports which since last work period, can not make change on the report dates.<\/li>\n<\/ul>\n

            Department Permissions<\/strong><\/h2>\n
              \n
            • Can Change Department: <\/strong>To the users who are created for this role, gives the authorization to work on departments. User; can work according to created role group authorizations.\u00a0<\/strong><\/li>\n<\/ul>\n

              \"\"<\/p>\n

              \"\"<\/p>\n

              2. Management Section Authorizations<\/strong><\/span><\/h2>\n

              Management Authorization; It is about roles that has been granted to access to management section. For this authorization write authorized category name and add related title after typing “.” (Period)<\/p>\n

              Example;<\/strong><\/p>\n

              Products.Product List
              \nProducts.Menu List
              \nProducts.Product Tag Editor
              \nProduct.Batch Price List
              \nUsers.User List
              \nPrinting.Printers
              \nPrinting.Printing Jobs
              \nPrinting.Printer Templates
              \nInventory.Movements
              \nInventory.Inventories
              \nInventory.Products
              \nInventory.Recipes
              \nEntities.Entities
              \nEntities.Batch Entity Editor
              \nEntities.Entity Screens
              \nSettings.Departments
              \nSettings.Terminals
              \nSettings.Currencies
              \nSettings.Database Backups<\/p>\n

              \"\"<\/p>\n

              When you perform the management section authorization like above example, only permitted titles will be displayed like in the image below.<\/p>\n

              \"\"<\/p>\n

              3. Mapping Authorizations<\/strong><\/span><\/h2>\n

              Beside user authorizations it’s also possible to perform role mapping on program functions. Role mapping titles are listed below.<\/p>\n

              Automation Commands<\/strong><\/span><\/p>\n

              Rules
              \nDocument Types
              \nTicket Tags
              \nOrder Tags
              \nPayment Methods
              \nChange Types
              \nCalculation Selectors
              \nProduct Timers<\/p>\n

              In the below sample getting payment\u00a0Automation Command Mapping only Admin, Manager and Cashier can get the payment, other roles can not.<\/p>\n

              \"\"<\/p>\n

              \"\"<\/p>\n","protected":false},"excerpt":{"rendered":"

              User roles are used to organise, limit and determine the roles and authoritiy of users. User can only see and perform process on the screens that related to own task area. User can not display and perform process on the screens that out of role. There are three stages for creation of authorization groups. Firstly […]<\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,14],"tags":[],"class_list":["post-9599","post","type-post","status-publish","format-standard","hentry","category-installation","category-2-2-sambapos-basic-setup"],"_links":{"self":[{"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/posts\/9599","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/comments?post=9599"}],"version-history":[{"count":13,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/posts\/9599\/revisions"}],"predecessor-version":[{"id":13672,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/posts\/9599\/revisions\/13672"}],"wp:attachment":[{"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/media?parent=9599"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/categories?post=9599"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kb.sambapos.com\/en\/wp-json\/wp\/v2\/tags?post=9599"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}