This article describes the existing permission resources (permissions to functions) and the permissions solution in Signifikant.
Permissions to functions
The below permissions are used to control access to functions within Signifikant.
Permission names | Description |
Administration | Access to administration module. |
AddToOrderCart | Access to add parts to order cart (‘add-to-order’ cart button). |
PlaceOrder | Access to place order and to MyOrders menu. This permission also allow user to save order. |
System | Default access. |
CompanyAdministration | Access to Create/update company details and create/update users and access to order received to company. |
Bulletin | Access to bulletin module. |
Feedback | Access to feedback module. |
MyAccount | Access to my account module. This permission also allows user to add notes if notes function is enabled. |
LoginPermission | Access to login. |
Synchronize | Access to synchronize data to offline viewer from web-viewer. |
Quotation | Access to create quotation. |
PartReplacement | Access to view Part replacement history. |
PriceDisplayModes | Users can choose to show discounts in settings. |
Groups
Permission resources consist of groups and these groups are applied to user. Groups can be shared between permission and as a result user belonging to the group will have access to permissions among which they are shared.
How to use permission resources and groups
Permissions to resources (functions or data) are connected to a group. Users being assigned to that group will have access to the resources in that group.
The connections between permissions and groups are defined in the permissions.config file. Which groups users belog to is defined by the user's credentials which may be fetched from Signifikant's database or from external solutions as an Active Directory.
Permissions.config
<Id>1</Id> | This is integer value written in incremental way. |
<Enabled>true</Enabled> | true or false will disable or enable Permission. If false, access control will be turned off for that function and users will be allowed to access the function. |
<Name>MyAccount</Name> | This holds the name of Permission resource. |
<Note>Users can access MyAccount settings</Note> | Description of permission. |
<Groups> | Groups hold the role applied to user. |
To apply permission or enable permission.Write the permission setting as per below example in permission.config file.
<ResourcePermission>
<Id>6</Id>
<Enabled>true</Enabled>
<Name>MyAccount</Name>
<Note>Users can access My Account settings</Note>
<Groups>
<string>EndClient</string>
</Groups>
</ResourcePermission>
<ResourcePermission>
<Id>7</Id>
<Enabled>true</Enabled>
<Name> Feedback </Name>
<Note>Users can access Feedback</Note>
<Groups>
<string>EndClient</string>
</Groups>
</ResourcePermission>
<ResourcePermission>
<Id>8</Id>
<Enabled>true</Enabled>
<Name>Bulletin </Name>
<Note>Users can Bulletin</Note>
<Groups>
<string>ServiceTeam</string>
</Groups>
</ResourcePermission>
In above example “EndClient” group is shared between Feedback and MyAccount whereas Bulletin is available to only groups called ‘ServiceTeam’.
Related articles