> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/commons/getting-set-up.md).

# Getting set up

This page explains how the subscription setup process works.

Overleaf Commons subscriptions are set up in collaboration with members of the Overleaf Support and Success teams.  As part of the onboarding process, the Overleaf Support team will provide technical assistance and help with [single sign-on](/commons/single-sign-on-sso.md) and [portal ](/commons/your-overleaf-portal.md)setup. Once the subscription is enabled, the Overleaf Success team will give an overview of the subscription's usage metrics and provide additional resources and information.

## The setup process

{% stepper %}
{% step %}

### Kickoff meeting

The Overleaf Commons onboarding process usually begins with a kickoff meeting to answer any questions you might have about your new subscription and how the setup works. During this meeting, we'll explain what information we need to set up the subscription, describe how we gather that information, and outline the steps in the subscription setup.
{% endstep %}

{% step %}

### Portal page setup

A Commons subscription comes with an Overleaf portal page—while these are optional, most customers choose to have one.  This customizable page provides:

* Information about your subscription, including who is eligible to join.
* Links to helpful information about how to use the service and access to key resources, including how to maximize the benefits of premium features and information about technical support.
* A direct link to your SSO login page (if you choose to have SSO), allowing users to easily register or log in to their Overleaf accounts.

{% hint style="success" %}
You'll need to provide us with information, images, and any wording that you want to include on your portal page.
{% endhint %}
{% endstep %}

{% step %}

### Single sign-on (SSO) setup

Overleaf Commons supports a standard SAML single sign-on (SSO) configuration. During the onboarding process, the Overleaf support team will provide you with configuration information and will assist in the setup of the SSO login option.

{% hint style="success" %}
We'll need to work with you and your IT team to get this up and running correctly. There's more about the information you'll need to provide in: [Single sign-on (SSO)](/commons/single-sign-on-sso.md)
{% endhint %}

{% endstep %}

{% step %}

### Launching your Commons subscription

Once everything is set up correctly, our Customer Success team will work with you to launch and promote the subscription to your users. If you would like to get a head start and begin working on custom promotional materials with our Customer Success team prior to completion of the technical setup, please [contact the Success team](mailto:success@overleaf.com) at your convenience
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.overleaf.com/commons/getting-set-up.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.