Skip to Content
AdminsOnboarding

Onboarding

We’re excited to get you up and running with Juno. Implementation typically takes under two weeks and requires only one meeting to complete most configuration.

Overview

Your onboarding will include the following steps:

Set up SSO

We provide a guided configuration dashboard for your IT team to configure and test your SSO connection. You’ll receive a link you can forward to your IT team. (Note: SSO is optional and not included in all plans.)

Set up your Juno Spend Account

Juno uses funds in your Juno Spend Account (JSA) to pay for travel purchases and approved out-of-pocket expenses. You will receive a monthly statement to reconcile this account and keep the balance above zero. To set up the account, we’ll collect basic business details and you’ll accept our banking partner’s terms.

Configure dashboard policies and preferences

Configure travel policy, expense policy, approval processes, custom fields, and saved locations in the dashboard. We’ll do this together during a guided call.

Your Roles

Three people typically participate in onboarding:

RoleDescription
Primary AdministratorThis is a person from your organization who we will work with to configure your dashboard during your Onboarding Call. This should be the most senior person who will still be directly involved in the operation of Juno.
IT AdministratorThis is a person at your organization responsible for internal technology operations, including, but not limited to, SSO.
Signing AuthorityThis is a person in your organization that has the authority to enter your company into binding legal agreements.

Timeline

Onboarding can take under two weeks if you can gather the required information promptly. We recommend the following sequence:

DayDescription
Day 1The Primary Administrator receives their Welcome Email (which is probably how you got to this document!)
Day 1-2The Primary Administrator forwards the SSO configuration link from the Welcome Email to the IT Administrator. Alternatively, we can send the link directly to an email you provide. This link enables full SSO configuration without an implementation call.
Day 1-7The Primary Administrator gathers pre-requisite information detailed in “Setting up your Juno Spend Account” and “Configuring dashboard with policies and preferences”. This information will be entered into your dashboard during the onboarding call.
Day 7-10Juno hosts a 1-1.5 hour Onboarding Call where the Primary Administrator logs into their new Juno account and we guide them through dashboard configuration. Missing information is okay—we’ll track outstanding items and provide a final checklist.
Day 10-14 (Optional)If needed, Juno sends a Final Onboarding Checklist of remaining items to be configured asynchronously in your dashboard.
Day 14+ (Optional)Juno can provide a 1-hour Coordinator Training session covering guest invitations, trip progress monitoring, and taking action on guest travel items.

Key Setup Components

1. Set Up SSO

We provide a dedicated configuration dashboard for your IT Administrator to set up SSO and Directory Sync connections. With provider-specific guides, your team can complete setup without lengthy email back-and-forth. The process is simple, fast, and secure.

A link to this configuration dashboard will be provided in your Welcome Email, which you can forward to your IT Administrator. We can also send this link directly to your IT Administrator if you supply us with their email.

If your IT Administrator has questions, share your Juno account manager’s contact information—we’re happy to help.

2. Set up your Juno Spend Account

Juno partners with Stripe Payments Company for money transmission services, with funds held at Fifth Third Bank. To open your JSA, we’ll (a) collect required business details and (b) confirm acceptance of partner terms.

2a. Collecting Business Details

For Public Companies

As most details about your organization are publicly available (legal entity name, legal address, EIN, revenues, etc.), we do not need to collect any of this information from you.

Instead, our banking partner needs a letter on company letterhead, signed by your Signing Authority, authorizing your Primary Administrator to administer your accounts and accept the banking terms of service (detailed in the next section).

Below is the format requested for this letter. Please copy the template below onto your letterhead.

[DATE]

[Company Name]

[Address]

To Whom it May Concern,

I, [Signing Authority Name], [Signing Authority Title], authorize account representative [Primary Administrator Name], [Primary Administrator Title] to manage this Stripe account.

Account ID(s): [Account ID; this will be provided to you]

Business name(s): [Company Name]

Website URL(s): [Company Website]

Business tax IDs: [Company Tax ID]

Thank you,

[Signing Authority Signature]

For Private Companies

The information requested during this process will vary depending on your organization ownership structure, but at a high level, we will request details such as legal company name, legal address, EIN, and company ownership structure.

We will collect as much of this information as we can during your Onboarding Call. You can provide any remaining details in the dashboard afterward.

2b. Accept Banking Terms of Service

During your Onboarding Call, you’ll accept our partners’ terms of service and disclosures. Links are provided below if your Signing Authority or legal team wants to review them in advance:

2c. Configure JSA Preferences

During your Onboarding Call, we’ll configure JSA preferences: top-up frequency, invoice recipients, and (if relevant) PO number.

3. Configuring Your Dashboard

During your Onboarding Call, we’ll configure your dashboard together, including policies, expense categories, custom fields, saved locations, and other key data.

We’ll explain each step. If information is missing, we’ll note it and follow up after the call with a Final Onboarding Checklist.

That said, we find that the Onboarding Call goes best when you collect and bring the following pieces of information:

  • Your preferred saved locations. You can load locations into Juno which will be common destinations for guest trips, such as your office locations. For a saved location, we need an address and a name (ex: “HQ” and “123 Main Street”).

  • Your travel policy for guests. This should include (a) what flights and hotels are allowed, (b) what hotels are preferred by your organization in common destinations, (c) what ground transportation is allowed, (d) whether companion travel is allowed, and (e) under what circumstances shoulder nights are allowed. You can have multiple different travel policies for different types of guests (for example, interns vs. VIP interview candidates).

  • Your expense policy for guests. This should include (a) what categories of expenses are allowed, (b) whether there are limits on amounts spent, (c) under what conditions receipts are required to accompany expenses, and (d) under what conditions memos are required to accompany expenses. You can have multiple different expense policies for different types of guests (for example, interns vs. VIP interview candidates).

  • Your preferred custom data fields. These fields can be collected from either your coordinators or your guests, and they will appear as columns in all of your transaction reports in Juno. For example, many organizations choose to collect information such as cost center to assist with booking purchases in their financial systems. These fields can be freeform text fields, single-select fields, or multi-select fields. In the case of single or multi-select, be sure to bring the values you want to be available as options.

Last updated on