Settings

Governance & billing

Nevika Labs · scale plan. Infrastructure controls for keys, permissions, policies, isolation and spend.

DEMO REFERENCE — this page shows illustrative governance, key, environment and billing examples. Real API keys, environments and policies live in Applications and Governance; real spend lives in Usage. Nothing on this page is live production data.

Permission model

APPLICATION→
USER→
RESOURCE→
ACTION→
PERMISSION

Permissions

ResourceActionApplicationModeScope
calendarreadPersonal AIallowall calendars
calendarwritePersonal AIaskprimary calendar
emailsendPersonal AIaskknown contacts
paymentsexecuteTravel AIask≤ £1,500
memorycreateTravel AIallowtravel namespace
browserexecuteWhatsApp AI Agentdenyall
knowledgereadCustomer Support AIallowkb_product

Policies

  • Execution policy · purchasesAsk

    Any tool with scope payments:write requires human approval above $250.

  • Access policy · memoryDeny

    Memory is readable only by the owning application. Cross-app reads are denied.

  • Retention policy · episodicScoped

    Episodic memory expires after 180 days unless promoted to semantic.

  • Execution policy · browserTemporary

    Browser agents run in an isolated session; downloads are quarantined.

Audit log

  • 14:41:02sam@nevika.iorotated api key uqp_sk_prod_••••4c2a
  • 13:08:55systemdenied memory.read across application boundary
  • 11:22:10ada@nevika.iogranted calendar:write to Travel Agent (staging)
  • 09:47:31systemapproval requested for payments:write execution

API keys & secrets

Illustrative examples — manage real keys under Applications

NameKeyEnvironmentScopesCreatedLast used
Personal AI · serveruqp_live_8f2c_••••production
query:writememory:rwagents:runtools:execute
2026-01-142 min ago
WhatsApp bridgeuqp_live_31ba_••••production
query:writeevents:writememory:read
2026-02-0218 min ago
Travel AI · staginguqp_stg_c704_••••staging
query:writeknowledge:rwworkflows:run
2026-03-214 h ago