---
title: "Configuring for Cloud"
canonical: "https://support.appfire.com/space/MARK/151158904/Configuring%20for%20Cloud"
format: markdown
---
> Macro (aura-html)

This page describes the various administrative functions available for all the macros available with the app. Select any of the following links for more information:

# Configuring the app

To access and get information from sources like GitHub, GitLab, and Bitbucket, you must create an OAuth 2.0 access token. This is done from the configuration page accessed from **Settings** (:conf_settings:) > **ATLASSIAN MARKETPLACE** (in the left sidebar) > **Markdown Extensions Configuration**.

![mdExt_cld_config.png](media://0d15821a-51c8-4dcf-b300-266be2320c26)

## Authorizing the app to access applications

This section describes how you can configure access to Github, Bitbucket, and Gitlab application, that is, the initial three tabs in the page. The process of authentication is similar regardless of the application to be accessed. 

You can perform the following actions on the tokens:

- For some reason, if need be, you can **Delete** a token. But, if you do so, all the macros that used this token will fail, and the pages will display errors. Thus, you must think carefully before using this feature.
- If, for any reason, a token expires or has issues, the page(s) with the macro(s) using this token will show errors. If so, click **Reauthorize** to create a fresh token. Doing so, does not affect the existing macros using this token.

Select the relevant application from below to know more:

### Authorizing app to access Github

First, you need to log in to your GitHub account, and then, allow access to the required repository or Markdown file. 

1. In the Markdown Extensions Configuration page, select the *Github* tab.
2. Type in a token name that’s easy to remember; then, click **Create New Link**.
3. An intermediate page opens:
  Check address of Atlassian cloud instance and token name. If everything looks correct, click **Start workflow** button.
4. Sign in to your Github account.
5. Next, an authorization page is shown. Click **Authorize**.<span style="color: #ff5630"> </span>If you have concerns about data and privacy, check out our [privacy policy](https://appfire.atlassian.net/wiki/x/KAFeM).
6. Next, provide the password of your GitHub account and click **Confirm**. With this, you are redirected to the configuration page.

After this, you should now be able to see your token in the list on the *Github* tab. You can add multiple accounts by logging in to a new Github account and allowing access to the required file. To make data private, you must provide permissions to the required repositories through Github.

### Authorizing app to access Bitbucket

First, you need to log in to your Bitbucket account, and then, allow access to the required repository or Markdown file. 

1. In the Markdown Extensions Configuration page, select the *Bitbucket* tab.
2. Type in a token name that’s easy to remember, and then, click **Create New Link**. This is similar to the step 1 mentioned under Github authorization section.
3. You are then redirected to the intermediate page.
  Check address of Atlassian cloud instance and token name. If everything looks correct, click the **Start workflow** button.
4. Next, you are redirected to an authorization page. Click **Grant Access**. If you have concerns about data and privacy, check out our [privacy policy](https://appfire.atlassian.net/wiki/x/KAFeM).

You're done! You can see your token in the list on the Bitbucket configuration page. You can add multiple accounts by logging into a new Bitbucket account and allowing access to the file.

### Authorizing app to access Gitlab

First, you need to authorize your Gitlab account from the configuration page.

1. In the Markdown Extensions Configuration page, select the *Gitlab* tab.
2. Type in a token name, and then, click **Create New Link**. This is similar to the step 1 mentioned under Github authorization section.
3. An intermediate page is shown:
  Check address of Atlassian cloud instance and token name. If everything looks correct, click the **Start workflow** button.
4. An authorization page is shown. Click **Authorize**. If you have concerns about data and privacy, check out our [privacy policy](https://appfire.atlassian.net/wiki/x/KAFeM).

After completing this, you can see your token in the list in the *Gitlab* tab. You can add multiple accounts by logging into a new Bitbucket account and allowing access to the file.

## Access tokens imported from server

This tab contains information regarding the tokens imported from server post migration. 

![mdExt_cld_config_accessTokenfrmServer.png](media://af232ad5-46a6-46bd-b9a4-82c74e8b3160)

See the [Migration guide](https://appfire.atlassian.net/wiki/spaces/MARK/pages/151158942/Migrating+from+Server+to+Cloud#Verification-post-migration) to learn more about how the tokens work after migration.

# Additional references

- [Migration guide](https://appfire.atlassian.net/wiki/x/noACCQ)
- [Macros overview](https://appfire.atlassian.net/wiki/x/U4BgM)