User Access

User access in NetX is managed via user levels, user groups, and permissions for folders and attributes. NetX supports several options for user account creation.

In this article Ask your team Extra help
Learn how user levels, groups, and permissions are used for access control so you can protect confidential or proprietary assets and data. You'll decide how many user groups you need, which actions users are allowed to perform, and how to create user accounts.

5 things to know about NetX users

NetX offers a two-dimensional approach to access control - user groups and user levels.
Permissions are granted by user groups — actions are controlled by user levels. Each user is assigned a single user level, but can belong to multiple user groups. This permission paradigm can be fine-tuned through advanced access control features in NetX.
User levels define the actions a user can perform.
The ability to view, download, edit metadata, create folders, delete assets, or alter site configurations are examples of actions that are controlled by user level. NetX has seven user levels available, ranging from No Access to Administrator (full access).
Permissions define where (on which assets) those actions can be performed.
Before users can perform actions on assets, they must be added to a group that is granted permission to access those assets. The many-to-many permissions model in NetX links groups of users to folders of assets. 
User groups aren't only for folder permissions.
User groups help facilitate many workflows in NetX, such as: sharing collections, searches, and reviews; requiring approval or justification for certain downloads; reporting on system use statistics; controlling view and edit permissions for attribute fields; or accessing API custom actions.
Your choice of authentication options.
Create NetX user accounts via manual entry, CSV spreadsheet import, end-user self-registration, SAML based single sign-on (SSO) integration, or Directory Server (LDAP) integration. Different authentication methods can be used simultaneously for different types of users (internal vs external). Portals can be set up for unauthenticated access.

Best practices

Keep it simple.
Add users to groups > add assets to folders > create permissions that link groups to folders. Even though you can add permissions to individual assets or users, we don't recommend it. 

Group users by access, not actions.
Create user groups based on the folders that different users need access to. Don't group users by the actions they need to perform — that's where user levels come into play. Groups can contain users with a myriad of user levels.

Expiration instead of deletion.
The user expiration date is helpful when creating temporary user accounts or when user access needs to be revoked. Expired accounts are automatically suspended instead of deleting the account entirely. This ensures statistical information relating to the deleted user is retained in the system.

Make it easy for users to sign up.
Flexible options for self-registered user accounts give you control over a user's initial access. New users can be allowed access to all content, a limited selection of content, or not allowed in at all until approved. If your organization already authenticates with single sign-on, consider an SSO integration for internal users to access NetX. 

Get everyone up and running at once.
If you're not using self-registration or SSO, Admins can easily import user data via .csv file to batch create new user accounts and pre-assign user levels and groups. NetX can automatically email new users and prompt them to set a password to log in to the system.


How-to articles

User accounts & access User workflows Advanced topics

Tips and tricks

End-users can manage their personal settings and profile information from the User Profile menu. They can also access Help and Contact links from this menu.

Use the filter box to quickly find information. In the systems area, the list of Users can be filtered by user name, email, or user level. You can also filter the Groups and Permissions lists to save time.

Set up a generic service user account that's maintained by your administrators. This account is not in use by any specific employee and will never be deleted or suspended. We recommend using a service account for: creating permanent share links, embed codesupload request links, and shared user attribute sets; for use with API or Hootsuite integrations; and when importing files via NetX I/O.

If using attribute-based Restrictions, configure the custom attribute and associated vocabulary first, then set up your Restrictions from the Groups window. To avoid unauthorized changes to the values, limit user access to the relevant attribute fields either by user-level or by user group with Attribute Permissions.

When a folder permission is created or altered, all assets in the system will be reindexed. Plan to execute configuration changes in off-peak hours since a full reindex may impact performance.

Manage new user passwords and email notifications via data file import. To set passwords on behalf of users and prevent the new user set-up email from going out, add a "Password" column and enter passwords for each user. If the "Password" column is omitted or left blank when new user accounts are imported using a data file, NetX will instantly send an email to prompt new users to set their own password.

To bulk send a password prompt email to existing users, export user data, then add a "Password" column leaving the values blank. Reimporting this data file will update existing users and trigger the password reset email. NetX Admins can also trigger password prompts to individual users by checking the "Autogenerate password" box in the User Account window.

BEFORE YOUR NEXT ONBOARDING MEETING

  • Meet with your Core Team to develop your permissions strategy.
  • Define groups for folder access and choose which user levels to employ.
  • Review your folder structure - changes may be needed for appropriate access control.
  • Identify any special authentication requirements.
  • Complete the User Access Onboarding Worksheet.
  • Be prepared to discuss with your Onboarding Specialist.

Up next...

Learn about Workflows and Settings.


BEFORE YOU IMPORT ASSETS
Review your permissions strategy with your Onboarding Specialist and read about File and Data Ingest.

Was this article helpful?
0 out of 0 found this helpful