# Divide up permissions

You sometimes need to divide up who can see and change what. For example: read-only for outside visitors, editing only their own posts for members, full management for teammates. **Tell the agent who should be able to do what, and it sets up the matching permissions.**

Permissions are defined by grouping them into **roles**. Operator roles and service member roles are separate.

## Tell your AI like this {#tell-your-ai}

> Connect this notes app to WEEGLOO. Let members see and edit only the notes they wrote themselves.

## What the AI then does {#what-the-agent-does}

1. Creates a role that allows only as much as is needed. It does not grant every permission from the start.
2. Applies an "only what they created themselves" condition, so a member can neither see nor edit someone else's notes.
3. Applies the role so each logged-in member can access only their own notes.

## Check that it worked {#how-to-check}

Log in as one member to check that only their own notes show, and try to edit another member's note to see if you are blocked. If you are blocked, the permissions are divided correctly.

![Divide up permissions](https://youtu.be/WLK7fHDTfJA)

## What to do next {#what-to-do-next}

- [Access and permissions](/getting-started/core-concepts/access-and-permissions.md): covers what roles and permission scopes are.
- [Show it publicly or only to your team](/ai/build/sharing.md): covers how to decide what to show to whom.
