> For the complete documentation index, see [llms.txt](https://releaseowl.gitbook.io/releaseowl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://releaseowl.gitbook.io/releaseowl-docs/releaseowl-user-guide/sap-analytics-cloud/analytics-cloud-management.md).
# Analytics Cloud Management
This section describes the process of configuring and managing **SAP Analytics Cloud (SAC)** environments in **ReleaseOwl**.
### **Adding SAC Environments to the Project**
The SAC environments must be registered in **Project Settings** in ReleaseOwl.
1. **To register SAC environment:**
* Go to the **Projects** drop-down at the top right corner and click **Project Settings**.
* In **Project Settings**, navigate to **Environment**.
* The following screen is displayed.
2. Click **Add** to add a new environment in ReleaseOwl.
* In the subsequent screen, select the required environments from the list displayed.
* Select **Source environment** and **Save** the changes.
{% hint style="info" %}
**Note:** Only the artifacts from the source are synced to ReleaseOwl.
{% endhint %}
3. The environment gets added to the corresponding project in ReleaseOwl.
4. Click on the **Users** tab. This tab lists all existing users associated with the project.4
5. Click on the **edit (lock)** icon next to the user for whom you want to manage roles and permissions.
6. This will open the **Permissions** page for the selected user.
7. Scroll down to the Environments section.
8. Check the Deploy checkbox for the relevant environment(s) to enable deploy access.
### **SAC Management and Deployment**
1. **Sync Packages:**
* Go to **SAC Management** in the **Build** section and click on **Sync Packages**.
* You can see the **Deployment History** by clicking on the **Actions** button and selecting **Deployment History**.
2. **View Package Details:**
* Click the **Actions** button and select **Import Settings** to view package details.
* Each package has different import settings, and you need to configure the import settings for the required package.
3. **Release Pipelines:**
* Go to the Release Pipelines and click on the **Create New Release Pipeline.**
* Enter a **Release** **Pipeline Name**.
* Click **Add Stage**.
* Enter the stage name say for e.g., UAT or QA where the deployment has to be carried out and click OK.
* **Tasks:** Click **Add** to enter any tasks that are to be performed
{% hint style="info" %}
**Note:** To remove any stage, click Remove stage button.
{% endhint %}
* Different tasks that can be added are as follows:
**Add a Deployment Stage**
* Click on **Add** under the **Tasks** section.
* Select **SAC - Deployment** from the available task types.
**Configure Task Details**
In the **Task Details** panel on the right side, fill in the following information:
| **Field** | **Description** |
| -------------------------- | ------------------------------------------------------------ |
| **Name** | Enter a unique name for your task. |
| **Description** | Optionally, provide a brief description of the task. |
| **Select SAC Environment** | Choose the SAC environment for deployment from the dropdown. |
**Optional Settings**
You may optionally configure the following:
* **Schedule Time**\
Enable this checkbox to schedule the deployment at a specific date and time.
* **Notify Users**\
Enable this checkbox to send email notifications to selected users after task execution.
* **Notify Promotion User**\
Enable this checkbox to notify the user who promoted the pipeline.
**Finalize the Task**
* Once all configurations are complete, click **Next** to proceed to **Step 3: Notification Email(s)** or continue adding more tasks as needed.
