Workspace settings
The workspace's settings are for its owners: the sidebar's Settings, a tab per section. The workspace's Overview shows them at a glance, with its credits, projects, team and what needs you.
Members
Add someone by their GitHub username, as a Member or an Owner, and Add. Change a role in the list, or Remove someone: they lose access to the workspace's board and its previews at once. You can't change your own role. See owners and members.
Credits
Every blueprint, build, prompt and answer uses credits as Maria works. Settings → Credits shows how many are left and a bar, and sells packs: pay once by card, no subscription, and the bigger the pack the less each credit costs. Credits never expire. The credits card in the sidebar turns amber when they run low and red at none.
Out of credits, a run already going pauses partway (Paused — out of credits; nothing is lost), and new work waits until you add credits and press ▶ Run again. Previews still start.
GitHub
- GitHub account or organization: where each project's private repository goes (
github.com/<owner>/<app-name>). Leave it empty to use the account of whoever runs the build. It has to be a GitHub account or organization that exists, not a folder. - Repo name prefix, put before every repository's name.
- Invite these GitHub users to every new repo, comma-separated.
A project gets its repository when its first build starts. Every build pushes as the person who ran it.
Connections
The outside accounts projects ship to. Each is checked when it's saved, and its keys never leave the server:
- Run your apps: AWS, Microsoft Azure, Google Cloud (see Deploy).
- Manage domains: Cloudflare (see Domains).
- Publish mobile apps: Expo EAS, Apple App Store, Google Play (see App stores).
Domains
The workspace's domains, to buy or use and give to apps. See Domains.
Vault
Keys, tokens and passwords, saved once for every project: a name (like STRIPE_SECRET_KEY) and its value, then Add secret. A project's Secrets tab picks what it needs from here. Each secret shows which projects use it, and can be replaced or removed. Values never leave the server.
Alerts
Send what happens to your projects to Slack, Discord, Microsoft Teams or any https webhook (up to 10 channels). Paste the channel's webhook address, give it a name if you like, pick what it gets, then Send a test and Add channel:
- A project moves to a new stage
- A step or prompt stops and goes back
- A prompt is built
- A prompt stops to ask you something
- A deployed app needs more resources
Alerts are the only notifications Neotexa sends; each links to the project.