# House rules and the Overview page - control all apps of an account

IT and security people need to see what the tools of their company are doing, and to set limits that no single app can undo. On Scava this is the **Overview** page of an account. It shows all apps of the account, everyone who can open them and every sign-in, and it holds the **house rules** that apply to all apps of the account. The house rules are enforced by Scava's server on every request. An agent or an app cannot change them.

The Overview page is part of the account of the person who builds the apps. There is no separate administrator sign-in for it. Rules, removals and groups can be changed only in the browser. A key held by an agent gets "please do it in the browser".

## What the Overview page shows

- **Apps.** Every app of the account with its version, who it is shared with, its co-editors and own address, where its data is kept (EU or US), how many outside services its server code talked to recently, and how many problems were reported for the live version.
- **People.** Everyone who can open the apps or has opened them, with when they last opened an app and how often, marked as inside the company or outside it. Removed people are listed too.
- **Sign-ins.** Every browser sign-in of the account with the kind of device, and every connected agent, with when it connected and when it was last used.
- **Activity.** The actions on the account's apps: creating, publishing, deleting, sharing, changing rules, removing people, connecting addresses, adding groups and co-editors.
- **Never the contents of apps.** Entries and files that people store in apps are not shown, and neither are reports.

## The house rules

| Rule | Values | What it does |
|---|---|---|
| Sharing outside the company | Anyone, partner domains only, nobody | Decides with whom apps may be shared. "Company" is the domain of the account's email address. The rule does not exist for accounts with a public mailbox such as gmail.com. |
| Outside services for server code | Any, only a list, none | Limits which services server code and heavy work may call. A list may contain patterns like `*.example.com`. |
| AI in apps | Any provider, EU only, off | Controls `env.SCAVA.ai()`. "EU only" allows Mistral and OpenAI with the key of an EU project. |
| Sign in again after | Never, 90 days, 30 days, 7 days | Forces people who open the apps to sign in again after that age. Without it, a sign-in is renewed while it is used. |
| Where new apps keep their data | EU, US | See [Data location](/docs/data-location). |

How the rules work:

- **The rules about sharing and services act at once and on every request.** Tightening "sharing outside" cuts off existing outside shares immediately. Loosening it brings them back. People outside see that the owner only shares inside their company.
- **Sign in again after** applies to people who open the apps, not to the owner. It is checked whenever an app session starts or renews, which is at least every 12 hours. If their sign-in is older than the setting, Scava sends them to sign in again. A person who left the company and lost their mailbox is out after that many days at the latest.
- **Outside services** are enforced on both ways out: server code and heavy work. The AI call follows the rule "AI in apps" instead. A refused call is recorded under "talks to". A version whose code names a service that is not allowed is refused when it is published.
- **Co-editors and groups** are also subject to the rules: nobody outside the allowed domains can be added.

## Remove a person from everything

On the Overview page, "remove person" takes one email address out of all apps of the account at once. It works also where an app is shared with a whole domain, which a normal "unshare" would not stop.

- Their own shares are removed.
- Their sessions in all apps end immediately.
- Open requests for access are declined, and apps stop sending them email.
- They are removed from all groups of the account and are no longer a co-editor.
- Sharing with their address again, or "let in again" on the Overview page, brings them back. A co-editor cannot do that on the side; only the owner.

## When someone leaves the company

Scava has no passwords. The mailbox is the key. When a person who built apps leaves, the company takes over the mailbox, signs in to Scava with a code and presses **Sign out everywhere else**. Every other browser session, every app session and every connected agent of that account is signed out at once. Only the browser that pressed the button stays signed in. The people who open the apps are not signed out by this; to keep one of them out, use "remove person". From there the company can remove people, change the rules, and download or delete apps.

This depends on the account address being a mailbox the company controls. If the apps were built under a private mailbox, the company has no access to it. Build under the company address.

## Groups

Groups give permission rules and sharing something more precise than "everyone". On the Overview page the owner creates a group, adds email addresses to it, removes them and deletes the group. Names use lowercase letters, digits, `-` and `_`. A group holds single addresses, not domains, up to 1,000 members, and an account can have up to 100 groups.

Groups are used in two places:

- in `scava.json` as `group:leads`; see [Permission rules](/docs/rules),
- as a share target of an app; see [Sharing](/docs/sharing).

The house rules apply to groups. An address outside the allowed domains cannot be added, and a removed person does not come back through a group.

## Several creators in one company

Each person who builds apps has their own account and their own Overview page. There is no view over the apps of several creators in one place. If that is important, let one company account build and maintain the shared tools, and add the others as [co-editors](/docs/co-editors).