> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/security-and-compliance/access-control/add-edit-or-delete-a-user.md).

# Network Segmentation

Create, edit, view, or delete users and assign appropriate roles

The DuploCloud Infrastructure construct maps to a VPC in AWS and GCP. In Azure, it maps to a VNET. Setting up the network is the first step, followed by the creation of DuploCloud Tenants, which are children of the DuploCloud infrastructure, as shown in the [policy model](broken://pages/HG00aWKRC4bAt07b2aUO). Kubernetes clusters are tied to the network and are part of this setup. For detailed guidance on infrastructure and network setup, refer to the individual cloud provider sections [AWS](/docs/automation-platform/overview/use-cases/creating-an-infrastructure-and-plan-for-aws.md), [Azure](/docs/automation-platform/overview-2/use-cases/infrastructure-and-plan.md), and [GCP](/docs/automation-platform/overview-1/use-cases/creating-an-infrastructure-and-plan-for-gcp.md) in their respective guides in this documentation set.

Subnets within a network infrastructure are tied to availability zones. A single application's multiple replicas are typically spread across multiple subnets. Subnets thus are not an isolation construct by default. However, you can deploy workloads in specific subnets when they launch the virtual machines. In the case of Azure, subnets also have special considerations, for example, different types of Azure PaaS services require their special subnets.

All resources in the cloud provider that allow resource provisioning to have a network interface associated are placed in private subnets. This is a straightforward configuration in AWS and GCP. In Azure, the platform deals with the more complicated workflows around creating private endpoints and hosted zones.<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/automation-platform/security-and-compliance/access-control/add-edit-or-delete-a-user.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.