Configure OneView

Load Data

In order to do the data load, you must have access to the data load feature in OneView. Specific services and support users have this access. If you do not and should, please have your manager contact Rich Jacobs and the OneView product team.

These instructions are for Enterprise accounts. Elite will be handled within Connect, more details soon!

1. Create an API user in the source system (Enterprise only):
   • When you create the API user, do not select Enforce Access Privileges.
   • If customer is not licensed for the API, enlist the help of the Licensing team:
     1. Send a new email to [e-mail]:
        • Include the environment URL and serial number.
        • Request a temporary add of the Basic API module.
     2. The Licensing Team (Sara N and Hope) will add the license and your ticket will be closed with public note to requester and followers, so you receive a notification.
2. Retrieve required API credentials: Org ID, Client ID, Secret, Base URL, User ID, Key.
3. In OneView: Navigate to the Data Load UI, add API credentials, and click Submit to begin loading.
4. If you requested temporary access to the API, either reopen the ticket (#reopen in the reply) or create a new ticket (email [e-mail]) to remove the API module.
5. Repeat steps 1-4 for each tenant that will be connected to Calendar Portal.
6. Log in to OneView using support user credentials.
7. Create first Customer Portal Admin Users: This initiates the Automated Entra Registration Flow. From this stage, configuration can be self-service if desired or provided by Support with a Portal Admin role.

Configure OneView

Steps 2-8 here correspond to the customer-facing steps in Getting Started with Momentus OneView.

1. Each customer must have at least one Portal Admin user created. This person has overall access to the OneView Instance and must be added first.
2. For each venue, the customer must determine who will be responsible for deciding which spaces/rooms will be available in OneView. This is usually a system admin at each specific venue or the Portal Admin.
3. If the customer wants to decentralize venues and space mapping, create a user for each of those people. Assign them the Venue Manager permission and select their venue as their venue portfolio.
   • See Manage OneView Users for more information and instructions.
4. The venue managers can log in and create their venue, selecting the rooms/spaces to make available and adding external-facing names if needed. (Note – this can also be handled by a Portal Admin from either the customer’s IT team or the Momentus Support Team).
   • See Manage Venues for more information and instructions.
5. While the venue managers are creating venues, map references so that data from different accounts and applications appears consistently in the calendar.
   • See Manage References for more information and instructions.
6. Once the venues are created, create User Group Templates. These can be created to assign a predefined set of permissions for venues.
   • See Manage User Group Templates for more information and instructions.
7. Once the groups are created, add general users, assigning them to the correct group so they have access to the correct venues.
   • See Manage OneView Users for more information and instructions.
8. If the venue managers should be able to view events on the calendar, assign a group to each one. Edit the user to assign a group, or assign a group to multiple users at once.
   • See Assign a User Group Template to Multiple Users for instructions.