# Can visitors see only published content, and staff only what's assigned to them?

Yes. In the Backend, each access rule can say which records it covers and, for changes, which fields. "anyone where status = published" lets visitors read published records only; "role:sales where assigned_to = me" lets sales staff see the records assigned to them; "role:sales where assigned_to = me only status" lets them change the status and nothing else. Describe it in plain words and Furge AI writes the rules, or edit the blueprint yourself. Furge checks each rule against your real columns, writes it into your database's row level security (a field limit is a database check on every change from the app), and before anything is applied tries it as each kind of person on a record that matches and one that doesn't. The API tab says who may change what. Rules can't yet say "or", a list of values, dates relative to today, or a condition through another table: those are listed as Can't build yet.

1. Turn on Developer at the top of the studio (or press Shift+D) and open Backend.
2. Describe who sees and changes what (for example: visitors see published pages; sales staff see and update the status of the enquiries assigned to them) and press Plan with Furge AI.
3. Open Tests: each person is tried on a record that matches each rule and one that doesn't.
4. Read Review, then Apply to database.

Also asked as: published only; only published; show only published content; hide drafts; keep drafts private; assigned to; staff see only their assigned enquiries; sales see only theirs; only change the status; which fields can staff change; field limits; only some records; only some fields; staff can update status only; notes in their own name

Page: https://furge.app/docs/backend-rules

## Related

- [What is the Requirements list in the Backend?](https://furge.app/docs/backend-requirements.md): When you describe your app's backend, Furge AI first lists what you asked for, one requirement for each thing, then designs the blueprint.
- [Does Furge check my database after it applies a change?](https://furge.app/docs/backend-verify.md): Yes.
- [Can my app's backend take a form, keep a status history and send emails?](https://furge.app/docs/backend-logic.md): Yes, on your own Supabase.
- [How do I turn my design into a working app?](https://furge.app/docs/build-app.md): Turn into… turns a design into a working website or app.

From Furge's docs: Apps and backends. Every answer, with a link: https://furge.app/llms.txt. All of them in one file: https://furge.app/llms-full.txt.
