# Create your TMS workspace

Right now, our team deploys every TMS workspace for you.\
You share your project details, we set up the infrastructure, and you receive a secure link to complete your portal configuration.

We’re working on a fully self-service deployment flow from our website; until that’s live, this is the **current production process**.

### Overview: from form to live TMS in \~24 hours

Creating your TMS workspace happens in three phases:

1. **Provide details for the agreement**\
   You submit your project details via our onboarding form so we can prepare the legal agreement and technical setup.
2. **Set up your TMS portal & connect your token(s)**\
   Once the agreement is signed, we deploy your TMS instance and send you an onboarding link where you confirm deployment details and connect your token.
3. **Set up your subdomain and customize your portal**\
   You configure the domain (e.g. `tokens.yourproject.com`) and apply your branding (logo, colors, links) so the portal feels fully native to your project.

Most projects go from **signed agreement → live TMS portal** in **under 24 hours**.

***

### Step 1 – Provide details for the agreement

To start, [fill in the onboarding form](https://share-eu1.hsforms.com/1y8xjyAi4Q0WKRB6EmqRmKQf5bmh) (currently hosted in HubSpot) that your TMS contact or partner shares with you.

In [this form](https://share-eu1.hsforms.com/1y8xjyAi4Q0WKRB6EmqRmKQf5bmh), we typically ask for:

* **Company and project information**
  * Legal entity name
  * Project/token name
  * Company website
* **Primary contact details**
  * Name
  * Email
  * Telegram / other preferred channel (if applicable)
* **Token and network**
  * Chain(s) you plan to use (e.g. Ethereum, BNB Chain, Polygon)
  * Whether your token is already deployed or not

We use this information to:

* Prepare the **service agreement**.
* Make sure your TMS deployment is planned on the **right network(s)**.
* Align timelines around TGE and launch.

Once you [submit the form](https://share-eu1.hsforms.com/1y8xjyAi4Q0WKRB6EmqRmKQf5bmh), our team sends you the agreement for signature.

***

### Step 2 – Agreement & deployment

After the agreement is signed, we schedule and deploy your dedicated TMS instance.

* Deployment is usually completed within **24 hours**.
* You don’t need to do any technical work at this stage.

When your instance is ready, we send you a **secure onboarding link**.\
This link opens the setup flow shown in the screenshot above (or a similar future version).

From here, you’ll complete three steps:

1. **Provide deployment details**
2. **Customize your subdomain**
3. **Customize your TMS portal**

The rest of this page explains what you’ll need for each step.

***

### Step 3 – Provide deployment details (onboarding link)

When you open the onboarding link, you’ll first see a **“Deployment details”** screen.

You’ll be asked for:

* **Company name**\
  The name that should appear in the admin panel and, where relevant, to your users.
* **Company website**\
  Used for context and sometimes linked from your public portal.
* **Your email**\
  For deployment confirmations and critical notifications.
* **Network**\
  The primary network for this TMS instance (e.g. Ethereum mainnet, BNB Chain).
* **Admin wallet**\
  The wallet that will be set as the **Admin** of your TMS contracts.

  > This wallet can add other Admins/Managers and, where applicable, withdraw funds from pools.\
  > For security, we strongly recommend using a **multi-signature wallet** here.
* **Token smart contract address**\
  The address of the token that this TMS instance will manage.

  > One instance = one token. If you have multiple tokens, you’ll use multiple workspaces.
* **Router address**\
  (If applicable) The address used for on-chain routing in your setup (often related to DEX/liquidity routing).
* **Optional links**
  * Terms & Conditions URL
  * Help & support URL (e.g. your docs or Telegram link)

Once these fields are filled in, you can **preview** your settings and confirm.

This step ensures the TMS smart contracts are connected to the **correct token, wallet, and network** before we finalize the deployment.

<figure><img src="/files/MSzYH8VyF3ysPBSxcmBa" alt=""><figcaption></figcaption></figure>

### Step 4 – Set up your subdomain (DNS)

Your TMS portal is served through our **white-label product**.\
This means your users don’t see a “tms.finance” URL — they see **your** domain, while we handle all hosting, infra, and costs behind the scenes.

A typical setup looks like:

> `https://staking.yourdomain.com` → your TMS portal\
> Infrastructure & hosting → managed by TMS

We do this by creating a **CNAME record** in your DNS.

#### What you’ll get from us

During onboarding we’ll ask which subdomain you want to use, for example:

* `staking.yourdomain.com`
* `tokens.yourdomain.com`
* `vesting.yourdomain.com`

You (or your tech team) then create a DNS record that points that subdomain to:

> `cname.vercel-dns.com`

After that, we handle:

* Hosting the portal
* SSL certificates
* Scaling and infrastructure

Your brand stays front and center; TMS stays under the hood.

<figure><img src="/files/VeEv6O5E4XzZXgq9ZtPR" alt=""><figcaption></figcaption></figure>

After this step, your TMS portal is accessible under **your own domain**, not a generic TMS URL.

#### How to configure your CNAME record

Follow these steps with your domain registrar or DNS provider (e.g. GoDaddy, Cloudflare, Namecheap):

1. **Log in** to your domain registrar or DNS provider.
2. Go to your **DNS settings**.
   * This may be called “DNS Settings”, “Manage DNS”, “Zone Editor”, “Advanced DNS”, etc.
3. Click to **add a new DNS record**.
4. Set the **record type** to `CNAME`.
5. In the **Name / Host** field, enter the subdomain you want to use:
   * For `staking.yourdomain.com`, enter just:\
     `staking`
6. In the **Value / Points To / Destination** field, enter:\
   `cname.vercel-dns.com`
7. **Save** the record.

That’s it. Once DNS propagates (usually within a few minutes, but it can take up to a few hours depending on your provider), your TMS portal will be reachable at the chosen URL, for example:

> `https://staking.yourdomain.com`

From there, you can continue with branding and content customization inside the TMS admin.

### Step 5 – Customize your TMS portal

The last step is to make the portal look and feel like an extension of your brand.

You can configure:

* **Branding**
  * Logo
  * Brand colors
  * Banners/hero images

Once you save these settings, your TMS instance is ready for operations:

* Admins and Managers can log in with their wallets.
* You can start creating **vesting strategies, locks, and staking pools**.
* Your public dashboard is available at your chosen subdomain.

### Coming soon – Self-service deployment

We’re working on a streamlined flow that will let you:

* Start from **tms.finance**
* Connect your wallet
* Create a workspace
* Configure deployment details, subdomain, and branding
* And go live **without manual back-and-forth**

When this launch-from-website flow is available, this page will be updated with the new steps. Until then, the **HubSpot + agreement + onboarding link** process described above is the **source of truth**.


---

# Agent Instructions: 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:

```
GET https://tms-finance.gitbook.io/tms.finance/getting-started/create-your-tms-workspace.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.