diff --git a/docs/integrations/aws.md b/docs/integrations/aws.md index c5d374b..c4c3259 100644 --- a/docs/integrations/aws.md +++ b/docs/integrations/aws.md @@ -5,7 +5,6 @@ sidebar_label: AWS # AWS Integration - The AWS Integration allows you to automatically import a connection folder hierarchy that mirrors your AWS Organization folder structure, with a connection folder for each AWS OU and a [connection](/pipes/docs/connections) for each account in your AWS organization. The AWS integration will automatically keep the configuration up to date as your organization changes, adding, removing, and modifying connections and folders as accounts and OUs are created, deleted, or changed in your AWS Organization. @@ -61,15 +60,9 @@ If desired, you can set advanced options for the child connections. These optio Click the **Test Connection** button to verify that the credentials are configured correctly, then click **Next**. -Finally, select the [Permissions](#permissions) to assign to the root folder created from this AWS integration. Note that you do not have to set the permissions now and you can change them later. - -- **All Organizations and Workspaces** -- **Specific Organizations and Workspaces** -- **No Workspaces** +Finally, select the [Permissions](/pipes/docs/tenants/connections#permissions). The permissions on this screen apply to the top-level folders and therefore to *all connections and folders* discovered by this integration. If you want to assign permissions more granularly, on a per-subfolder or per-connection basis, select **No Workspaces** at this time, and then manage the permissions on the connections and folders once they have been discovered. -The permissions on this screen apply to the root folder and therefore to *all connections and folders* discovered by this integration. If you want to assign permissions more granularly, on a per-subfolder or per-connection basis, select **No Workspaces** at this time, and then manage the permissions on the connections and folders once they have been discovered. - -Note also that **All** will not only add permissions for the existing identities and workspaces but will also allow access for any new connections and folders that are created when they are added to the AWS organization. +Note also that **All** will not only add permissions for the existing identities and workspaces but will also allow access for any new connections and folders that are created when OUs or accounts are added to the AWS organization. After you have made your selections, click **Create Integration**. Pipes will begin discovering your accounts and OUs and creating folders and connections. @@ -105,16 +98,4 @@ Navigate to the **Integrations** page for the appropriate resource: - To configure an AWS integration for your **Organization**, click the double arrow button from the organization switcher at the top of the page and select the organization from the dropdown. Once you've selected your organization, go to the **Integrations** tab to manage the integrations for the organization. -Go to the **Advanced** page and click the **Delete Integration** button. You will be asked to enter the handle to confirm deletion. If you wish to *permanently delete the integration and all of its resources*, click **Delete**. - - -## Permissions -You can create an integration for a tenant or an organization, and where you create the integration affects the scope of the resources it creates; the resulting connections and folders can only be shared within the entity in which it was created. When creating the integration, you can set **Permissions** for the connections and folders that it creates: - - Tenant-level connections and folders can be shared with any identity or workspace within the tenant. - - Org-level connections and folders can be shared with any workspace within the org, but not with other orgs. - -When you grant permissions on a folder, all the connections that are members of that folder inherit the same permissions; granting access to a folder implicitly grants access to its connections. Permissions are additive and can only be granted, not denied. If you grant permissions to an identity or workspace for a folder you cannot revoke access for these individual connections, only to the folder as a whole. - -You can set permissions for folders and connections from their settings page. Navigate to the desired tenant or org and browse the **Connections** to find the resource you wish to manage. Click the connection or folder. From the **Settings** tab, select **Permissions**. Select the desired permissions and click **Save**. - -Note that setting permissions for a connection or folder does not attach its schema to the workspaces, it merely makes it visible to the workspaces so that [it may be attached](/pipes/docs/connections#adding-schemas). +Go to the **Advanced** page and click the **Delete Integration** button. You will be asked to enter the handle to confirm deletion. If you wish to *permanently delete the integration and all of its resources*, click **Delete**. \ No newline at end of file diff --git a/docs/integrations/azure.md b/docs/integrations/azure.md index e13f01a..2eb46ea 100644 --- a/docs/integrations/azure.md +++ b/docs/integrations/azure.md @@ -48,15 +48,9 @@ Optionally, provide a **Handle Prefix** to be pre-pended to the names of connect Click the **Test Connection** button to verify that the credentials are configured correctly, then click **Next**. -Finally, select the [Permissions](#permissions) to assign to the root folder created from this Azure integration. Note that you do not have to set the permissions now and you can change them later. +Finally, select the [Permissions](/pipes/docs/tenants/connections#permissions). The permissions on this screen apply to the top-level folders and therefore to *all connections and folders* discovered by this integration. If you want to assign permissions more granularly, on a per-subfolder or per-connection basis, select **No Workspaces** at this time, and then manage the permissions on the connections and folders once they have been discovered. -- **All Organizations and Workspaces** -- **Specific Organizations and Workspaces** -- **No Workspaces** - -The permissions on this screen apply to the root folder, thus *all connections and folders* discovered by this integration. If you want to assign permissions more granular, on a per-subfolder or per-connection basis, select **No Workspaces** at this time, and then manage the permissions on the connections and folders once they have been discovered. - -Note also that **All** will not only add permissions for the existing identities and workspaces but will also allow access for any new connections and folders that are created when they are added to the Azure organization. +Note also that **All** will not only add permissions for the existing identities and workspaces but will also allow access for any new connections and folders that are created when subscriptions or management groups are added to the Azure organization. After you have made your selections, click **Create Integration**. Pipes will begin discovering your subscriptions and management groups and creating folders and connections. @@ -93,17 +87,4 @@ Navigate to the **Integrations** page for the appropriate resource: - To configure an Azure integration for your **Organization**, click the double arrow button from the organization switcher at the top of the page and select the organization from the dropdown. Once you've selected your organization, go to the **Integrations** tab to manage the integrations for the organization. -Go to the **Advanced** page and click the **Delete Integration** button. You will be asked to enter the handle to confirm deletion. If you wish to *permanently delete the integration and all of its resources*, click **Delete**. - - - -## Permissions -You can create an integration for a tenant or an organization, and where you create the integration affects the scope of the resources it creates; the resulting connections and folders can only be shared within the entity in which it was created. When creating the integration, you can set **Permissions** for the connections and folders that it creates: - - Tenant-level connections and folders can be shared with any identity or workspace within the tenant. - - Org-level connections and folders can be shared with any workspace within the org, but not with other orgs. - -When you grant permissions on a folder, all the connections that are members of that folder inherit the same permissions; granting access to a folder implicitly grants access to its connections. Note that permissions are additive and can only be granted, not denied. If you grant permissions to an identity or workspace for a folder you cannot revoke access for these individual connections, only to the folder as a whole. - -You can set permissions for folders and connections from their settings page. Navigate to the desired tenant or org and browse the **Connections** to find the resource you wish to manage. Click the connection or folder. From the **Settings** tab, select **Permissions**. Select the desired permissions and click **Save**. - -Note that setting permissions for a connection or folder does not attach its schema to the workspaces, it merely makes it visible to the workspaces so that [it may be attached](/pipes/docs/connections#adding-schemas). +Go to the **Advanced** page and click the **Delete Integration** button. You will be asked to enter the handle to confirm deletion. If you wish to *permanently delete the integration and all of its resources*, click **Delete**. \ No newline at end of file diff --git a/docs/integrations/gcp.md b/docs/integrations/gcp.md index c368fa0..5f9f255 100644 --- a/docs/integrations/gcp.md +++ b/docs/integrations/gcp.md @@ -38,17 +38,11 @@ Optionally, provide a **Handle Prefix** to be pre-pended to the names of connect Add your **Credentials**, in the form of a JSON key pair for an existing [GCP service account](https://console.cloud.google.com/apis/credentials/serviceaccountkey). As a minimum, grant your service account the **Viewer** role in the projects and folders that you wish to manage. -Finally, select the [Permissions](#permissions) to assign to the root folder created from this GCP integration. -- **All Organizations and Workspaces** -- **Specific Organizations and Workspaces** -- **No Workspaces** +Finally, select the [Permissions](/pipes/docs/tenants/connections#permissions). The permissions on this screen apply to the top-level folders and therefore to *all connections and folders* discovered by this integration. If you want to assign permissions more granularly, on a per-subfolder or per-connection basis, select **No Workspaces** at this time, and then manage the permissions on the connections and folders once they have been discovered. -The root connection folder will contain all connections and sub-folders for this integration, and sharing the root folder will share the full tree, including all of its connections. If you wish to assign permissions more granularly (on individual connections or folders), select **None** and then assign the permissions on those connections and folders after they have been created. - -Note also that **All** will not only add permissions for the existing identities and workspaces but will also allow access for any new connections and folders that are created when they are added to the GCP organization. - -After you have made your selections, click **Create Integration**. Pipes will begin discovering your projects and folders and creating folders and connections. +Note also that **All** will not only add permissions for the existing identities and workspaces but will also allow access for any new connections and folders that are created when folders and projects are added to the GCP organization. +After you have made your selections, click **Create Integration**. Pipes will begin discovering your subscriptions and management groups and creating folders and connections. ## Modifying the GCP Integration @@ -81,17 +75,4 @@ Navigate to the **Integrations** page for the appropriate resource: - To configure an AWS integration for your **Tenant**, click the double arrow button from the tenant switcher at the top of the Pipes console, select your tenant, and then select **Tenant Settings**. This option will only be visible in a custom tenant for which you are a [tenant owner](people#tenant-roles). Once you've selected your tenant, go to the **Integrations** tab to manage the integrations for the tenant. - To configure an AWS integration for your **Organization**, click the double arrow button from the organization switcher at the top of the page and select the organization from the dropdown. Once you've selected your organization, go to the **Integrations** tab to manage the integrations for the organization. -Go to the **Advanced** page and click the **Delete Integration** button. You will be asked to enter the handle to confirm deletion. If you wish to *permanently delete the integration and all of its resources*, click **Delete**. - ----------- - -## Permissions -You can create an integration for a tenant or an organization, and where you create the integration affects the scope of the resources it creates; the resulting connections and folders can only be shared within the entity in which it was created. When creating the integration, you can set **Permissions** for the connections and folders that it creates: - - Tenant-level connections and folders can be shared with any identity or workspace within the tenant. - - Org-level connections and folders can be shared with any workspace within the org, but not with other orgs. - -When you grant permissions on a folder, all the connections that are members of that folder inherit the same permissions; granting access to a folder implicitly grants access to its connections. Note that permissions are additive and can only be granted, not denied. If you grant permissions to an identity or workspace for a folder you cannot revoke access for these individual connections, only to the folder as a whole. - -You can set permissions for folders and connections from their settings page. Navigate to the desired tenant or org and browse the **Connections** to find the resource you wish to manage. Click the connection or folder. From the **Settings** tab, select **Permissions**. Select the desired permissions and click **Save**. - -Note that setting permissions for a connection or folder does not attach its schema to the workspaces, it merely makes it visible to workspaces so that [it may be attached](/pipes/docs/connections#adding-schemas). +Go to the **Advanced** page and click the **Delete Integration** button. You will be asked to enter the handle to confirm deletion. If you wish to *permanently delete the integration and all of its resources*, click **Delete**. \ No newline at end of file diff --git a/docs/org-connections.md b/docs/org-connections.md index a41c168..b74d62e 100644 --- a/docs/org-connections.md +++ b/docs/org-connections.md @@ -9,9 +9,9 @@ A **[Connection](/pipes/docs/connections)** represents a set of tables for a **s You can organize connections into **Connection Folders**. This makes it easier to share groups of connections across workspaces in your tenant or organization. -Connections and folders that are created at the organization level can be shared with any workspace in the organization. You must be assigned the organization **Owner** role to create, modify and delete organization connections and folders. +Connections and folders that are created at the organization level can be [shared](#permissions) with any workspace in the organization. You must be assigned the organization **Owner** role to create, modify and delete organization connections and folders. -You can create connections and folders manually, but they may also be created by [integrations](/pipes/docs/integrations/). For example, the [AWS](/pipes/docs/integrations/aws), [Azure](/pipes/docs/integrations/azure), and [GCP](/pipes/docs/integrations/gcp) integrations create and manage folders and connections automatically to mirror the organizational structure of your cloud provider. You can manage permissions to share these connections and folders just like the ones you create manually, but note that folders that are created by integrations are only managed by the integration; you cannot add or remove sub-folders or connections from them. +You can create connections and folders manually, but they may also be created by [integrations](/pipes/docs/integrations/). For example, the [AWS](/pipes/docs/integrations/aws), [Azure](/pipes/docs/integrations/azure), and [GCP](/pipes/docs/integrations/gcp) integrations create and manage folders and connections automatically to mirror the organizational structure of your cloud provider. You can manage [permissions](#permissions) to share these connections and folders just like the ones you create manually, but note that folders that are created by integrations are only managed by the integration; you cannot add or remove sub-folders or connections from them. ## Managing Connections @@ -25,27 +25,15 @@ This view will include all the connections that the organization has permission You can create connections from the **Connections** tab for your organization. The connections page displays the folder connection tree hierarchically. To add a connection or folder, first navigate to the folder in which to create the new folder or connection. -To create a new folder, go to the folder in which you would like to create the new folder, then click the **New Connection** button and select **New Folder**. Give your folder a **Name** and click **Create**. Next, you are prompted to set permissions on the folder. When you grant permissions on a folder, you also grant permissions for all of its descendent folders and connections. This simplifies managing groups of connections across your organizations. Choose workspaces that can use this folder and all of its connections: -- All organization workspaces -- Specific organization workspaces -- No workspaces +To create a new folder, go to the folder in which you would like to create the new folder, then click the **New Connection** button and select **New Folder**. Give your folder a **Name** and click **Create**. Next, you are prompted to set [permissions](#permissions) on the folder. When you grant permissions on a folder, you also grant permissions for all of its descendent folders and connections. This simplifies managing groups of connections across your organizations. Choose the desired permissions and click **Save**. -Click **Save**. - -To create a connection, navigate to the folder in which you would like to create the connection, then click the **New Connection** button and select **New Connection**. Select the **Plugin**, enter a **Handle**, and enter any plugin-specific settings. Click **Test Connection** to verify your credentials, then **Create** to create the connection. Next, you are prompted to set permissions on the connection. You may set permissions on individual connections but remember that they also inherit the permissions of their parent folder; setting **No Workspaces** on the connection does not remove permissions if they have been granted on a parent folder, it merely does not grant permission on the individual connection. Choose workspaces that can use this connection: -- All organization workspaces -- Specific organization workspaces -- No workspaces - -Click **Save**. - +To create a connection, navigate to the folder in which you would like to create the connection, then click the **New Connection** button and select **New Connection**. Select the **Plugin**, enter a **Handle**, and enter any plugin-specific settings. Click **Test Connection** to verify your credentials, then **Create** to create the connection. Next, you are prompted to set [permissions](#permissions) on the connection. You may set permissions on individual connections but remember that they also inherit the permissions of their parent folder; setting **No Workspaces** on the connection does not remove permissions if they have been granted on a parent folder, it merely does not grant permission on the individual connection. Choose the desired permissions and click **Save**. Organization-level connections are confined to the organization in which they are defined, and they cannot be shared with other organizations. If you wish to re-use a connection across organizations, you can create [tenant-level](/pipes/docs/tenants/connections.md) connections and folders instead, and assign permissions to share them with specific organizations or workspaces. Tenant connections can be created or deleted from the **Connections** tab for your tenant. You can create connections and folders manually, but they may also be created by [integrations](/pipes/docs/integrations/). For example, the [AWS](/pipes/docs/integrations/aws), [Azure](/pipes/docs/integrations/azure), and [GCP](/pipes/docs/integrations/gcp) integrations create and manage folders and connections automatically to mirror the organizational structure of your cloud provider. You can manage permissions to share these connections and folders just like the ones you create manually, but note that folders that are created by integrations are only managed by the integration; you cannot add or remove sub-folders or connections from them. - ## Deleting Connections To permanently delete a connection, navigate to the **Connections** tab for your organization. Browse the connection tree, and click the gear icon for the connection that you wish to delete. On the **Settings/Advanced** tab, click **Delete Connection**. You will be prompted to confirm deletion. Enter the connection handle then click **Delete Connection**. @@ -55,3 +43,32 @@ To delete a folder, click the gear icon for the folder that you wish to delete. You cannot delete folders or connections that were created by an [integration](/pipes/docs/integrations/) - they are automatically managed by the integration. Tenant-level connections and folders must be deleted from the **Connections** tab for the corresponding tenant. + + +## Permissions + +Connections defined at the organization level can be shared with any workspace in the organization. Organization-level connections are confined to the organization in which they are defined, and they cannot be shared with other organizations ([Tenant-level connections](/pipes/docs/tenants/connections) provide this capability). + +You can make connections available to workspaces by setting permissions, either on individual connections or folders. When you grant permissions on a folder, all the folders and connections that are members of that folder inherit the same permissions; granting access to a folder implicitly grants access to its sub-folders and connections. Note that permissions are additive and can only be granted, not denied. If you grant permissions to an identity or workspace for a folder you cannot revoke access for these individual connections, only to the folder as a whole. + +You can set permissions for folders and connections from their settings page. Navigate to the desired tenant or org and browse the **Connections** to find the resource you wish to manage. Click the gear icon for the connection or folder you would like to permission. From the **Settings** tab, select **Permissions**. + + +***THis will change...*** + +Select the desired permission: +- All workspaces +- Specific workspaces +- No workspaces + +Click **Save**. + + +You may set permissions on individual connections but remember that they also inherit the permissions of their parent folder; setting **No Workspaces** on the connection does not remove permissions if they have been granted on a parent folder, it merely does not grant permission on the individual connection. Choose workspaces that can use this connection: +- All organizations and organization workspaces +- Specific organizations and/or organization workspaces +- No workspaces +***End*** + + +Note that setting permissions for a connection or folder does not attach its schema to the workspaces, it merely makes it visible to the workspaces so that [it may be attached](/pipes/docs/connections#adding-schemas). \ No newline at end of file diff --git a/docs/tenants/connections.md b/docs/tenants/connections.md index 3dbc4f2..379faf0 100644 --- a/docs/tenants/connections.md +++ b/docs/tenants/connections.md @@ -4,19 +4,18 @@ sidebar_label: Connections --- - A **[Connection](/pipes/docs/connections)** represents a set of tables for a **single data source**. To query data, you'll need at least one connection to provide credentials and other configuration information. -You can organize connections into **Connection Folders**. This makes it easier to share groups of connections across workspaces in your tenant. +You can organize connections into **Connection Folders**. This makes it easier to [share](#permissions) groups of connections across workspaces in your tenant. Connections and folders that are created at the tenant level can be shared with any workspace or organization in the tenant. You must be assigned the tenant **Owner** role to create, modify and delete tenant connections and folders. -You can create connections and folders manually, but they may also be created by [integrations](/pipes/docs/integrations/). For example, the [AWS](/pipes/docs/integrations/aws), [Azure](/pipes/docs/integrations/azure), and [GCP](/pipes/docs/integrations/gcp) integrations create and manage folders and connections automatically to mirror the organizational structure of your cloud provider. You can manage permissions to share these connections and folders just like the ones you create manually, but note that folders that are created by integrations are only managed by the integration; you cannot add or remove sub-folders or connections from them. +You can create connections and folders manually, but they may also be created by [integrations](/pipes/docs/integrations/). For example, the [AWS](/pipes/docs/integrations/aws), [Azure](/pipes/docs/integrations/azure), and [GCP](/pipes/docs/integrations/gcp) integrations create and manage folders and connections automatically to mirror the organizational structure of your cloud provider. You can manage [permissions](#permissions) to share these connections and folders just like the ones you create manually, but note that folders that are created by integrations are only managed by the integration; you cannot add or remove sub-folders or connections from them. ## Managing Connections -You can manage your tenant's connections and folders from the **Connections** tab. Navigate to your tenant, then to the **Connections** tab. The connections page will show all the tenant-level connections and folders in the tenant, arranged hierarchically, and you can click on folders to navigate the folder tree. +You can manage your tenant's connections and folders from the **Connections** tab. Navigate to your tenant by clicking the double arrow button from the tenant switcher at the top of the Pipes console. Select your tenant, and then select **Tenant Settings**. This option will only be visible in a custom tenant for which you are a [tenant owner](people#tenant-roles). The **Connections** tab will show all the tenant-level connections and folders in the tenant, arranged hierarchically, and you can click on folders to navigate the folder tree. This view will include all the connections and folders in the tenant, including connections and folders that are created by integrations. Note that the resources created by an integration are dynamically managed by the integration and cannot be manually modified. @@ -25,31 +24,47 @@ This view will include all the connections and folders in the tenant, including You can create connections from the **Connections** tab for your tenant. The connections page displays the folder connection tree hierarchically. To add a connection or folder, first navigate to the folder in which to create the new folder or connection. -To create a new folder, go to the folder in which you would like to create the new folder, then click the **New Connection** button and select **New Folder**. Give your folder a **Name** and click **Create**. Next, you are prompted to set permissions on the folder. When you grant permissions on a folder, you also grant permissions for all of its descendent folders and connections. This simplifies managing groups of connections across your tenant. Choose workspaces that can use this folder and all of its connections: -- All organizations and organization workspaces -- Specific organizations and/or organization workspaces -- No workspaces - -Click **Save**. +To create a new folder, go to the folder in which you would like to create the new folder, then click the **New Connection** button and select **New Folder**. Give your folder a **Name** and click **Create**. Next, you are prompted to set [permissions](#permissions) on the folder. When you grant permissions on a folder, you also grant permissions for all of its descendent folders and connections. This simplifies managing groups of connections across your tenant. Choose the desired [permissions](#permissions) and click **Save**. -To create a connection, navigate to the folder in which you would like to create the connection, then click the **New Connection** button and select **New Connection**. Select the **Plugin**, enter a **Handle**, and enter any plugin-specific settings. Click **Test Connection** to verify your credentials, then **Create** to create the connection. Next, you are prompted to set permissions on the connection. You may set permissions on individual connections but remember that they also inherit the permissions of their parent folder; setting **No Workspaces** on the connection does not remove permissions if they have been granted on a parent folder, it merely does not grant permission on the individual connection. Choose workspaces that can use this connection: -- All organizations and organization workspaces -- Specific organizations and/or organization workspaces -- No workspaces +To create a connection, navigate to the folder in which you would like to create the connection, then click the **New Connection** button and select **New Connection**. Select the **Plugin**, enter a **Handle**, and enter any plugin-specific settings. Click **Test Connection** to verify your credentials, then **Create** to create the connection. Next, you are prompted to set [permissions](#permissions) on the connection. You may set permissions on individual connections but remember that they also inherit the permissions of their parent folder; setting **No Workspaces** on the connection does not remove permissions if they have been granted on a parent folder, it merely does not grant permission on the individual connection. Choose the desired [permissions](#permissions) and click **Save**. -Click **Save**. - Tenant-level connections are confined to the tenant in which they are defined, and they cannot be shared with other tenants. You can create connections and folders manually, but they may also be created by [integrations](/pipes/docs/integrations/). For example, the [AWS](/pipes/docs/integrations/aws), [Azure](/pipes/docs/integrations/azure), and [GCP](/pipes/docs/integrations/gcp) integrations create and manage folders and connections automatically to mirror the organizational structure of your cloud provider. You can manage permissions to share these connections and folders just like the ones you create manually, but note that folders that are created by integrations are only managed by the integration; you cannot add or remove sub-folders or connections from them. - ## Deleting Connections To permanently delete a connection, navigate to the **Connections** tab for your tenant. Browse the connection tree, and click the gear icon for the connection that you wish to delete. On the **Settings/Advanced** tab, click **Delete Connection**. You will be prompted to confirm deletion. Enter the connection handle then click **Delete Connection**. To delete a folder, click the gear icon for the folder that you wish to delete. On the **Settings** tab, click **Delete Folder**. You will be prompted to confirm deletion. Enter the folder title, then click **Delete Folder**. -You cannot delete folders or connections that were created by an [integration](/pipes/docs/integrations/) - they are automatically managed by the integration. \ No newline at end of file +You cannot delete folders or connections that were created by an [integration](/pipes/docs/integrations/) - they are automatically managed by the integration. + + +## Permissions + +Connections defined at the tenant level can be shared with any organization or organization workspace in the tenant. Tenant-level connections are confined to the tenant in which they are defined, and they cannot be shared with other tenants. + +You can make connections available to workspaces by setting permissions, either on individual connections or folders. When you grant permissions on a folder, all the folders and connections that are members of that folder inherit the same permissions; granting access to a folder implicitly grants access to its sub-folders and connections. Note that permissions are additive and can only be granted, not denied. If you grant permissions to an identity or workspace for a folder you cannot revoke access for these individual connections, only to the folder as a whole. + +You can set permissions for folders and connections from their settings page. Navigate to the desired tenant or org and browse the **Connections** to find the resource you wish to manage. Click the gear icon for the connection or folder you would like to permission. From the **Settings** tab, select **Permissions**. + +Select the desired permission: +- All organizations and organization workspaces +- Specific organizations and/or organization workspaces +- No workspaces + +Click **Save**. + + +***THis will change...*** +You may set permissions on individual connections but remember that they also inherit the permissions of their parent folder; setting **No Workspaces** on the connection does not remove permissions if they have been granted on a parent folder, it merely does not grant permission on the individual connection. Choose workspaces that can use this connection: +- All organizations and organization workspaces +- Specific organizations and/or organization workspaces +- No workspaces +***End*** + + +Note that setting permissions for a connection or folder does not attach its schema to the workspaces, it merely makes it visible to the workspaces so that [it may be attached](/pipes/docs/connections#adding-schemas). \ No newline at end of file