Think of a Connection as a user group. Your content, or more specifically, your Card(s) will need to be assigned a connection and any user you want to view your Card(s) will also need to be assigned the same connection.
This method helps you separate or isolate your content between different users. For example, you can create your Cards and then assign them a reviewer connection. Then assign a small reviewer group the reviewer connection. Another example would be to assign five out of ten Cards to an 'employee" connection, and the other five Cards to a manager connection.
Read below for information on how to create a connection and assign it to a Card and then assign it to a user.
Create your Connection
To create a connection, expand the Access section in the main left navigation, and click on the Connections section. This will bring up the list of connections. This section will be empty if you are just beginning. Click on the Create Connection button located at the top right of the screen.
This will bring up the Add Connection modal. The modal has options to customize your connection.
Channel: You can choose which main organization will own this connection. This is to isolate the administrators. This is a Super-Admin feature only.
Name: Give your connection a unique and descriptive name.
Notes: You can provide any notes to remind you or other admin what this connection is for.
Content Code: You are able to provide any code you would like. A user could then simply type in that code from their app, and they will be given the connection.
Deep Link Path: You can paste in a URL from the app side of a specific location of a Deck or Card, then when a user types in the content code or scans the QR code related to the connection, they will be taken to that specific location.
Active: You are able to toggle on/off the active state of the connection.
Use Active Dates: This toggle brings up a calendar where you can set an active start date and an end date to deactivate the connection.
Allow Guest Access: If toggled on, when a user scans the related QR code, they will bypass the login screen. This is beneficial if you have an SSO set up, but would like to have public content.