diff --git a/docs/explore-and-analyze-data/owner.svg b/docs/explore-and-analyze-data/owner.svg
index 01489c7e5e..e9abfa2663 100644
--- a/docs/explore-and-analyze-data/owner.svg
+++ b/docs/explore-and-analyze-data/owner.svg
@@ -21,7 +21,6 @@
-
@@ -346,35 +345,6 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/install-ai-unlimited/setup-ai-unlimited.md b/docs/install-ai-unlimited/setup-ai-unlimited.md
index 52c2e4a630..88037e68a4 100644
--- a/docs/install-ai-unlimited/setup-ai-unlimited.md
+++ b/docs/install-ai-unlimited/setup-ai-unlimited.md
@@ -26,7 +26,7 @@ For setup support, ask the [community](https://support.teradata.com/community?id
## Complete the fields
-***(changes being made to the UI - info in these sections could change)***
+***(changes to the UI - info in these sections is back to WIP)***
Find information about each group of fields here.
@@ -107,17 +107,25 @@ Select **Update**.
-***(new fields to be added)***
-
**Default region**—The Azure region in which to deploy the engine. We recommend choosing the region closest to your primary work location.
+**Default network resource group** **(verifying)**
+
+**Default network** **(verifying)**
+
+**Default subnet** **(verifying)**
+
+**Default key vault** **(verifying)**
+
+**Default key vault resource group** **(verifying)**
+
**Inbound security**
Use these fields to allow source traffic to reach the engine:
- **Default [CIDRs](/docs/glossary.md#glo-cidr)**
-- **Default [application security group](https://learn.microsoft.com/en-us/azure/virtual-network/application-security-groups) names**—If you deploy the engine in the same Virtual Private Cloud as AI Unlimited, include the AI Unlimited application security group in this field to ensure that AI Unlimited can communicate with the engine.
+- **Default [application security group](https://learn.microsoft.com/en-us/azure/virtual-network/application-security-groups) names**— **(verifying field label)** If you deploy the engine in the same Virtual Private Cloud as AI Unlimited, include the AI Unlimited application security group in this field to ensure that AI Unlimited can communicate with the engine.
**Resource tags**—You can [tag](https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/tag-resources) the Azure resources that deploy the engine to make them easier to manage.
@@ -140,13 +148,15 @@ Select **Update**.
-***(might add GitHub application URL & GitHub callback URL pending discussion)***
+**GitHub application URL**—The manager uses this URL to connect to the GitHub account to authenticate a user.
+
+**GitHub callback URL**—After authenticating a user, GitHub uses this URL to redirect back to the manager.
**GitHub base URL**—The URL for your GitHub account.
**GitHub client ID** and **GitHub client secret**—The credentials received from GitHub when your [OAuth app was created](/docs/install-ai-unlimited/git-requirements.md).
-**GitHub username**—Your GitHub username.
+**GitHub login**—**(this field might be removed)**
**Organization access**
@@ -157,6 +167,8 @@ Two organizations in your GitHub account can help with access control and reposi
- Project repositories are created in the **Repository organization**. If you don't specify an organization, projects will be in your personal GitHub space.
+Select **Update**.
+
Select **Login**. Then, if prompted, sign in.
@@ -164,10 +176,17 @@ Select **Login**. Then, if prompted, sign in.
+
+**GitLab application URL**—The manager uses this URL to connect to the GitLab account to authenticate a user. **(verifying)**
+
+**GitLab callback URL**—After authenticating a user, GitLab uses this URL to redirect back to the manager. **(verifying)**
+
**GitLab base URL**—The URL for your GitLab account.
**GitLab client ID** and **GitLab client secret**—The credentials received from GitLab when your [OAuth app was created](/docs/resources/git-requirements.md).
+**GitLab login** **(verifying)**
+
**Group access**
Two groups in your GitLab account can help with access control and repository management:
@@ -177,7 +196,9 @@ Two groups in your GitLab account can help with access control and repository ma
- All project repositories are created in the **Repository group**. If you don't specify a group, projects will be in your personal GitLab space.
-Select **Authenticate**. Then, if prompted, sign in.
+Select **Update**.
+
+Select **Login**. Then, if prompted, sign in.
diff --git a/docs/manage-ai-unlimited/add-collaborators.md b/docs/manage-ai-unlimited/add-collaborators.md
index e94a753fe4..a537925fdf 100644
--- a/docs/manage-ai-unlimited/add-collaborators.md
+++ b/docs/manage-ai-unlimited/add-collaborators.md
@@ -10,16 +10,20 @@ pagination_next: null
# Add project collaborators
-If you are the project owner, you can add collaborators to your project. The steps depend on whether or not the engine is deployed.
+If you are the project owner, you can add collaborators to your project. The steps depend on whether you do this before or after the engine is deployed.
## Before the engine is deployed
-In GitHub or GitLab, add users to the project repository. ***(might add more info about this)*** When you deploy the engine from your JupyterLab notebook, the users are added to the engine automatically.
+1. In GitHub or GitLab, add users to the project repository.
+See details about adding repo users for [GitHub](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository) or [GitLab](https://docs.gitlab.com/ee/user/project/members/#add-users-to-a-project).
+
+2. When you deploy the engine from your JupyterLab notebook, the users are added to the engine automatically.
## After the engine is deployed
1. In GitHub or GitLab, add users to the project repository.
+See details about adding repo users for [GitHub](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository) or [GitLab](https://docs.gitlab.com/ee/user/project/members/#add-users-to-a-project).
2. In your JupyterLab notebook, run the magic command `%project_engine_update_users` to add the users to the engine.