This article describes the Nexus GO Cards management portal for ordering ready-to-use cards, key fobs and accessories. The Nexus GO Cards management portal is available at https://cards.nxsas.com/.
To get access to the Nexus GO Cards management portal, the service must first be ordered from Nexus, see Contact Nexus.
The Nexus GO Cards management portal is available in several languages and the look and feel can be customized for your organization. Here you order cards and accessories. You can select company if you have registered several companies.
Read more about the available security features, technologies etc for the cards here: Nexus GO Cards visual security features.
The Nexus GO Cards management portal consists of the following standard functions:
Use the Cards tab to order your cards. The organization's pre-configured card designs are shown. Depending on the card package selected, you can fully customize your card, and select additional security features. In the portal you can preview cards and accessories, upload and edit an image, approve and track orders and more.
Use the Accessories tab to order card holders and other accessories.
In the Manage orders tab, you can see the order history and search for orders.
In the Administration tab you can add and delete delivery addresses and manage users.
You have the possibility to set up a retention period for your organization. Currently you have the choice to have order data removed/anonymized after 3, 6 or 12 months (default: no retention period). Once your data passes the retention period threshold, personal data such as names, photos, addresses etc. will be removed. For a complete list, see Anonymization in Nexus GO Cards Management portal.
If you wish to setup a retention period go to this page https://www.nexusgroup.com/contact/ and select "Product information and demo" as reason for contact.
These are the additional functions that can be added to the Nexus GO Cards management portal:
If you have this additional function in the Nexus GO Cards management portal, you can select to print the cards locally, on a card printer at your premises, as an alternative to order the cards from Nexus.
The functionality will be available with the Print now button in parallel with Add to cart when you order your cards. You manage printing and the printers under the Printing tab.
With the additional self-service function, you can send an email to one or more employees to invite them to add information for a specified card layout and potentially upload a photo by themselves. This function is found under the Invites tab.
When you send an invite, the employee receives an email with a personal link. The link takes the recipient to a web page where information corresponding to the layout can be added, and a photo can either be uploaded or taken. The photo can be adjusted directly on the web page and after that the invitation is confirmed.
You, as orderer/inviter can follow the information in the portal and see when there is a card ready for you to approve. You can also select to send reminders if an employee has not yet filled in the card information or lost the invitation.
After a card has been personalized or activated, a report can be created with the card data, including readouts.
The Reports function is found under the Administration tab.
The report can, for example, be used for import into existing physical access systems when activating the cards. The report is created as a generic csv or ARX xml file and can be downloaded directly from the Nexus GO Cards management portal. The content of the report file is specified as part of the onboarding process.
For alternative ways of retrieving the card report data see Nexus GO Cards reporting.
With the additional Nexus REST API you can integrate an internal process or system like an HR, identity management or access control system with the Nexus GO Cards service. With the REST API, the ordering process will be integrated into your own system. Read more here: Card ordering API.
When added, the necessary credentials and associated information about the API function is found under the Administration tab.
With the additional card activation function, each card is associated with the card recipient's email address. This adds another layer of security, since the card recipient verifies that he or she has received the card, and then activates it.
This is the flow:
- An email is sent to the card recipient with a personal link to the self-service portal.
- The card recipient receives the card and a receipt containing the personal activation code.
- The card recipient clicks on the link in the email and follows the instructions to activate the card.
By using the card activation function, the card report data availability is postponed until the card has been activated.
Federated login is used for Single Sign-On and ordering support.
Nexus GO Cards support Openid Connect and Azure AD login. The configuration of Federated login is done in OIDC under the Administration tab.
Nexus GO Cards uses groups in the Openid Connect userinfo response to assign the user's roles in the Nexus GO Cards management portal. The roles are assigned to the user based on the mapping in the OIDC configuration.
This is an example of a response in userinfo:
Roles and permissions
For more information on the available roles and their permissions in Nexus GO Cards management portal, see this link: