Index
Section: Setting Menu > Security > Roles
FAQS
Introduction
In this article we will see how to give premises to different users according to their role.
The first thing we would have to do is to create the different types of profiles, and then assign them to each user in the system. This will make it so that each employee can or cannot access certain pages or perform certain tasks.
General
To create a new role type follow the steps below:
Name: Here we will put the name for this type of role. For example "Reception".
IP Addresses: You may optionally enter the IP addresses to which this custom role should be assigned.
Remarks: Here you can optionally add some text to help you describe what this role does.
Once we save the changes, a new section will be enabled at the bottom, where we will be able to activate certain permissions.
Permissions
To go faster you can select the "Disable all" or "Enable all" buttons as needed.
You will see that there are 2 columns or levels. The first level is access or not to the specific plugin. In the second level (only in the few plugins that have it, for example billing) we will mark what can be done within that plugin. That is, I can allow the waiter to enter the POS to charge, but I do not allow him to cancel sales.
In Golfmanager we have been adding tasks to this list according to demand. Notify the support team if there is any action within a specific plugin that you need to limit.
Special mention would have the last two permissions, edit configuration and users, which are actions that are usually activated only in 1 or 2 users of the system in each club.
Note: If you want to create a read-only user, this is not done from roles. It is done when creating the new user, by clicking on "Read only".
We explain below what each point consists of:
Activities: Allows you to enter, view, and modify the activities (events) module.
Administrators and Roles: Allows you to enter, view, and modify the system administrators module. It is usually activated only for system administrators.
Auto Check-in: Allows you to use the auto check-in tool for your reservations. It is usually activated only for the reception.
Help: Allows you to view the help articles. This plugin will disappear soon as it will be replaced by Intercom (the blue support bubble).
Search engine: Allows the user to search for anything in Golfmanager (customer, product, type of reservation, etc.) using the search engine in the header of Golfmanager. It can be activated for everyone as it is not a risk.
Custom Fields: Allows you to enter, view, and modify the custom fields module. It is usually activated only for system managers.
Contacts: Allows to enter, view, and modify customer cards. It is usually activated for everyone.
Quotas: Allows to enter, view, and modify customer quotas. It is usually activated to everyone or only to the partners department if there is one.
Labels: Allows to create store product labels.
Billing: Allows to enter the POS to sell items and billing lists. Within this module it has been necessary to specify "sub tasks":
Update price: Allows to edit the price of an item in a specific sale. Not to be confused with changing the price of a product forever. It may be convenient at the beginning of using Golfmanager, that perhaps the rates are not fully configured, that employees can quickly change a rate to not depend on a manager to do so.
Add discounts: Allows to add discounts to sales at the POS. It is usually limited to waiters so that discounts cannot be made without permission. It would need a manager with another role to be able to apply a discount.
Cancel lines: Allows to cancel sales of a POS. It is usually used in the restaurant so that a waiter cannot delete some article. What the waiters usually do in this case is to move a sale to a "discard table" and then the manager deletes them definitively.
Modify voucher balance: Allows the user to manually modify the balance of a customer's voucher units or purse through the customer's card. This function is no longer in use as we are looking to unify these movements through the POS.
Modify sales with date of use in the past: This option requires the advanced option billing.requirePermissionToUpdatePastSales to be activated and would allow a user to edit a sale that has already passed. At Golfmanager we advise that you should be able to change the past sale and only look at the billing, which is always up to date.
Modify sales created in the past: This option requires the advanced billing.requirePermissionToUpdatePastCreatedSales option to be enabled and would allow a user to edit a sale created in the past.
Reload vouchers with different price than the reload: Allows editing the units and price when selling a voucher or units. At the beginning of using Golfmanager it is usually activated since it is often necessary to import vouchers from the previous system.
Require the customer to have credit to sell on credit: activating this option forces the system user to pay for sales on credit only if the customer has this option activated in his file. It is usually more agile for reception to NOT have this option activated.
Golf: Allows to enter, view, and modify some listings made for the golf industry.
Customer Libraries: Internal use.
Notes of the day: Allows to enter, view, and modify notes of the day. It is usually not at risk and is usually enabled for everyone.
Relationships: Allows to enter, view, and modify customer friendships so that customers can book faster on the web, widget or app. It is usually activated for everyone.
Reservations: Allows to enter, view, and modify reservations in the system. Access to this module is usually given to the reservations department, although other departments will likely need to have visibility for organization.
Unrestricted check-in: Allows check-in to reservations without validating some default rules (that it is paid, that it is on the day, etc.). This option is not usually activated.
Remove check-in to reservations: Allows to remove check-ins to reservations. It is usually used to control that the reception does not remove reservations from the schedule once the check-in has been done.
Online Reservations: Allows access to the Golfmanager online reservations module. It is usually activated in all roles.
Stock: Allows to enter, view and modify the stock module (orders, inventories...). It is usually activated for users responsible for the store. If this option were not activated, the user would still be able to sell in TPV, but not to operate with orders, inventories, etc.
Stripe: It allows to enter, to see, and to modify the configuration of stripe. It is usually activated only for system administrators.
Pivot tables: Allows to enter, view, and modify the pivot tables module. It is usually activated for managers and management.
Online Store: Allows access to the Golfmanager online booking cart. It is usually activated in all the roles.
POS: It allows to enter to the TPV of Golfmanager to sell and to charge articles. It is usually activated in all the roles.
Translations: Allows to enter, view, and modify the translations of the system. It is usually activated for everybody, only in courses outside Spain to solve some erroneous word.
Customer Zone: Allows you to enter the Golfmanager online booking area. It is usually activated in all roles.
Edit configuration: Allows you to edit any configuration of a module in Golfmanager. It is important that this option is only activated in the role of managers.
Edit users: Allows to modify user profiles, personal data, passwords and permissions. It is important that this option is only activated in the responsible role.
Do not allow by role to modify past sales
To disable the role option of not allowing past sales to be modified, follow these steps
Click on Configuration Menu > Security > Administrator > Role ID desired.
Deactivate the field modify sales with date of use in the past.
Save
Allow / Do not allow per role "edit configuration".
In the Configuration Menu (cogwheel).
Click on Security.
Click on Roles.
Find and open by clicking on the id the corresponding role.
Activate / Deactivate the tab "Edit configuration".
Save.