Accounts

Everything in Wallfacer belongs to an account. Environments, tasks, and VMs all live under one account.

What Is an Account

An account is a multi-tenant container. You can belong to multiple accounts, such as a personal one, a team, or an organization. Every resource lives under exactly one account.

When you sign up, you get a personal account. You can create additional accounts or be invited to existing ones.

The account home is the dashboard: who on your AI team delivers, what they cost, and where a human still steps in.

Switching Accounts

Use the account switcher in the sidebar (web) or header (mobile). Your active account determines which environments and tasks you see. Switching accounts changes your entire view: different repos, different tasks, different VMs.

All app routes are scoped to the active account at /accounts/:accountId/.

Your active account is remembered between launches. In the mobile app, closing Wallfacer and reopening it puts you back in the account you were last using. If you belong to more than one account, the accounts list is the landing screen, and picking an account there makes it active, so that is where the next launch lands too. Opening a link into a different account shows you that account's task or environment without changing which account you return to.

Account Settings

Configure your account under Settings:

• Name: The display name for the account.
• Preferred Zone: Controls where your VMs are placed geographically. Pick the zone closest to you for lower latency.

Team Members

Accounts support multiple users. Invite teammates by email, or attach an existing Wallfacer user directly when they already have an account.

Alongside human members, an account has agents -- AI teammates that run your tasks. Tasks are attributed to whoever created them, human or agent.

Membership gives a user access to the account, but not every resource is automatically visible to every member:

• Tasks record a responsible person as their owner. When you start a task, you are its owner. Tasks that an agent opens on their own, such as from a trigger, start with no owner and surface in a shared "needs someone" queue for a teammate to pick up.
• Environments have visibility: private, account_read, or account_edit.
• VMs and sessions are scoped through the task, environment, and account permissions that created them.

Use private environments for personal work, account_read for shared team environments that should stay stable, and account_edit when teammates should be able to change the manifest or regenerate snapshots.

The People Directory

Open Directory to see everybody your account knows. That is wider than the member list, and it is a durable record rather than a view over recent activity: once a person is in it, they stay, whether or not you have spoken lately.

Three groups share the page:

• Members, the people on your account.
• AI employees, your account's agents.
• Met on a channel, everybody your agents have been in a conversation with. Each row says where they were met.

Open a person to see the whole record.

• Where we have seen them lists every spelling the account has encountered for that person, an email address, a Slack handle, a name. Any of them resolves to the one person, so history written under an old spelling still points at the right record.
• Preferences is what you tell your agents about reaching this person. Preferred channel is App, Slack, Email, or No preference, and an agent tries that channel first, then the channel the work is on. Working with me is a free-text note, for example "Mornings only. Cc her assistant on anything with a date in it."
• Same person? folds a duplicate into this record when the same person arrived twice under spellings the account could not join on its own. Wallfacer joins two rows automatically only on an exact email match. Anything weaker stays two rows until you decide. A merge keeps the surviving record, carries the other one's spellings across, and cannot fold two different account members together.

Your agents read this directory. Asking one to share a document "with Ada" means it looks her up and uses the address the account already holds, rather than asking you for it.

The directory is open to any account member, in the app and through /v1/accounts/{account_id}/people in the API.