Ordering AppDat

AppDat Customer Onboarding #

Step 1: Contact the MCP #

MCP: agcy-missioncloud@mail.nasa.gov

When MCP receives your request, they will initiate contact to arrange an ‘Overview’ meeting involving your team and MCP management. During this session, you’ll discuss and ascertain the number of seats needed for your group, along with identifying the most suitable AppDat Support option for your requirements. Following this, Ben Cahoon, the AppDat project manager, will contact you to schedule a tenant onboarding meeting

NOTE: Customers will need to know how many AppDat Gitlab users their organization will need.

Step 2: Open AppDat Gitlab NAMs requests launch #

Once the AppDat tenant on-baording process is completed , customers need to open the AppDat Gitlab NAMs requests for each user that within the organization that will be using AppDat. There are four roles within the NAMs workflow:

  1. Maintainer: civil servant organization management, and/or senior level contractors trusted with administration of the organization’s AppDat group with Gitlab.

  2. Developer: developers are responsible for source code but cannot administer the organization Group itself

  3. Reporter: reporters are typically project managers, business analysts, testers, project stakeholders who monitor or support project management with Issues, Epics, Milestones, etc…

  4. Guest: this role is ideal for individuals who need to view, but not contribute to, the content. Guests can typically create issues, leave comments, and view basic project details.

NOTE: When choosing your tenant organization in the NAMS request select whether you are a general user or apart of tenant leadership.

For more information on the AppDat user roles see here

Getting started #

See the following developer guides to start using AppDat services: