Downcity
Security & Permissions

Security and Permissions Overview

User-facing security model for isolation, chat authorization, and secret protection

Security and Permissions Overview

Downcity security has three layers:

  1. Agent isolation: one running agent is bound to one projectRoot.
  2. Chat authorization: user roles decide who can send messages into the agent.
  3. Data protection: model provider apiKey is encrypted in ~/.downcity/downcity.db.

What to watch first

  1. Avoid stale DC_CITY_HOST/DC_CITY_PORT in your shell, or requests may hit the wrong agent.
  2. New users fall into the lowest authorization group by default, so review chat roles before rollout.
  3. In production, prefer DC_MODEL_DB_KEY from secret management.
  1. API Authentication
  2. Permissions
  3. Data Security and Keys
  4. Invocation Routing and Isolation