> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/appendix/brokerage-set-up/transaction-management-deals/skyslope-forms.md).

# SkySlope Forms

Because SkySlope forms libraries are managed at the Group ID level, setup planning is extremely important before onboarding begins.

***

## Before You Begin

### Key Operational Considerations

#### Group IDs Control Brokerage Form Libraries

Brokerage forms populate at the SkySlope Group ID level.

Every user under that Group ID shares the same brokerage forms library.

#### Users Cannot Belong to Multiple Brokerage Libraries

A single user can only belong to one brokerage forms library at a time.

The Team Switch feature does not switch brokerage form libraries.

#### Plan Regional & Office Libraries Carefully

Before connecting to SkySlope, determine:

* Whether different offices require unique forms
* Whether different states require separate libraries
* Which users belong to which Group IDs

Once connected, all users under that Group ID inherit the same brokerage forms library.

***

## Types of SkySlope Forms

### MLS / Association Forms

MLS and Association forms are added automatically during onboarding. Some MLSs require agents to enter their NRDS ID for authorization.

### Brokerage-Specific Forms Libraries

Brokerages may also upload custom brokerage forms through SkySlope.

Examples include:

* Internal disclosures
* Brokerage-specific transaction forms
* Office compliance documents

{% hint style="info" %}
Additional SkySlope fees may apply.
{% endhint %}

{% hint style="info" %}
Form development may take 2–4 weeks.
{% endhint %}

***

## Brokerage Form Requirements

Brokerage forms:

* Must be PDF files
* Must be brokerage-specific
* Cannot contain watermarks, stamps, or provider branding
* Must be named exactly as they should appear in the library

MLS and Association forms should not be submitted through this process.

***

## Existing SkySlope Clients

If your brokerage already uses SkySlope, roster mapping should be completed before onboarding to prevent duplicate accounts. SkySlope will need to provide a roster export for mapping.

***

## Setup Process

### Step 1 — Map Existing SkySlope Rosters (If Applicable)

For existing SkySlope clients:

1. Request a roster export from SkySlope
2. Coordinate roster mapping before onboarding users

This prevents duplicate accounts from being created.

### Step 2 — Connect SkySlope & Generate Group ID

An admin should:

1. Navigate to Deal Settings
2. Connect to SkySlope
3. Complete the onboarding flow

Completing onboarding generates the SkySlope Group ID.

If separate offices or regions require unique forms libraries, generate separate Group IDs by connecting SkySlope in that region or office, before onboarding users at the root brand level.

### Step 3 — Submit Brokerage Forms Request

Email: <rechatforms@skyslope.com>

Include:

* Brokerage Name
* Rechat Group ID(s)
* Brokerage Forms Admin Contact
* Brokerage Billing Contact

{% hint style="info" %}
Please note that there are mapping fees associated with this process.
{% endhint %}

Submitted forms must:

* Be brokerage-specific
* Be PDF files
* Not contain watermarks or provider branding

### Step 4 — Agent Onboarding

New agents should complete the standard SkySlope onboarding process. Existing SkySlope users will automatically be added to the mapped group.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.rechat.com/appendix/brokerage-set-up/transaction-management-deals/skyslope-forms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.