[Index]
To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com
Administrators above Provider level can maintain access profiles as a part of role management. For example, hcsadmin.
An access profile assigned to a role provides a general set of permissions and type-specific operations that are associated with specific models.
For type-specific operations, wild cards may be used in model references, for example data/*.
Note
Type-specific permissions that are also configured as general permitted operations will override the general permissions.
The default access profiles show typical configurations, for example an Operator-type profile at a hierarchy would only require Read type-specific permissions, while the administrator profile at the same hierarchy would have Create, Update and Delete permissions for the same type.
The default access profiles of the following administrators above Provider level have full general and type-specific permissions to all models:
The lists below provide details on the types of settings.
Miscellaneous Permissions
Many of these are general permissions that can be overridden per model as Type Specific Permissions.
The explanations below show the affect of enabling the permission.
Type Specific Permissions
These are typically available on the GUI when listing or showing the type.
Note
Typical operations are listed below:
Create, Delete, Read, Update: management operations on models.
Configuration Template, Field Display Policy: create these for the model.
Export, Export Bulkoad Template : allow export formats of the model.
Bulk Update: from a GUI list view, more than one item can be selected and updated.
For system level administrators above provider level: Purge for device models. From a list or instance view, remove the local database instance but retain it on the device.
Note
This operation is only applicable in cases where the UC server is still online and available in the VOSS Automate system.
For designers: Migration: a migration template can be obtained.
For designers: Tag and Tag Version: a model instance can be tagged and a version provided.
Related Topics
Introduction to Access Profiles in the Core Feature Guide
Access profiles define model types that a user is permitted to access. Access profiles are assigned to users via Roles
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name * | The name that is given to the Access Profile. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description | A description for the Access Profile. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Full Access | Enabling this flag, grants the user full system access. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Miscellaneous Permissions | The list of miscellaneous operations permitted by this Access Profile. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Type Specific Permissions | The list of types that are permitted by this Access Profile. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Permitted Type * | The type that is permitted by this Access Profile. This field supports the use of the * wildcard. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Permitted Operations | The operations that are permitted by this Access Profile for the given type. |
|