Documentation

A Space is a web app that Viktor builds and hosts for your workspace: a dashboard, an internal tool, a tracker or a customer-facing site. Each Space has its own database, sign-in and hosting. Use a Space when the app needs to store data or run server logic. For a report or write-up that only needs a shareable link, publish a hosted page instead.

Build a Space by asking

1. Describe the app to Viktor in Slack, Teams or the web app. For example: "Build an internal tool where the sales team can log demo requests and see them by week."
2. If your request leaves out details that matter, Viktor asks his questions in one message before he starts.
3. Viktor builds the app, tests it and takes screenshots.
4. When he is done, he posts the screenshots, the app's URL and a summary of what he built or changed.

To change the app later, keep talking to Viktor in the same way: "add a CSV export to the demo tracker" or "make the chart show the last 90 days." He updates and redeploys the existing Space.

Start from the web app

You can also start from Spaces:

1. Select Create space.
2. In Create a space, pick one of the starting points, or select Start from scratch.
3. You land in chat with the prompt filled in. Edit it if you like, then send it.

Nothing is created until you send the message. Create space only appears when web chat is available in your workspace (see Viktor web app).

Preview and production

A Space can have two deployments, and each one has its own database:

• Production is the live app. Put real data here.
• Preview is for trying changes before they go live. It uses a separate database. Previews show a Viktor Space preview badge with the warning "Do not put real or private information here. Use the live app for that."

By default, Viktor deploys an internal app (one that needs sign-in) straight to production. For a public app that anyone can open without signing in, he deploys to preview first and asks for your approval before he deploys production. This is how Viktor is instructed to work, not a rule the platform enforces, so say so if you want a different order.

Viktor only builds a public app when you confirm that the app doesn't need sign-in. Who can open the URL is a separate setting; see Space access and domains.

Ask Viktor about your app's data

Ask Viktor questions such as "how many people signed up this week?". He answers by running one of the app's existing queries against the production database, or the preview database if you ask for it.

Queries that need a signed-in user return "Not authenticated" when Viktor runs them. To see that data, use the Database tab (below).

Manage Spaces in the web app

Open Spaces to see every Space in your workspace.

• Switch between grid and list view. Your browser remembers the choice.
• Use Search spaces, filter by creator, and filter by Status: Production, Preview or Not deployed.
• Sort by Recently created, Recently updated, Recently deployed or Name (A–Z).
• Pin a Space with its star. Pinned Spaces are listed first.
• Select Open app to open the live app.

If your workspace has no Spaces yet, the page shows "Create beautiful sites and apps" and suggests asking Viktor to build one.

A Space's detail page

Select a Space to open its detail page. It has up to four tabs:

• Overview: the app's Production and Preview links.
• Database: browse the app's data, functions and logs. Switch between Production and Preview. Only the Space's creator and workspace admins see this tab.
• Access: who can open the app. See Space access and domains.
• Settings: the app's name, description, URL, link preview image, favicon and custom domains, and the Danger zone.

The Name and Description fields can't be edited in Settings yet. The page says: "The name and description aren't editable here yet. For now, ask Viktor to change your app's name, description, or SEO tags and redeploy."

Favicon and link preview

In Settings, the Space's creator or a workspace admin can:

1. Under Favicon, select Upload to set the icon shown in the browser tab (256×256 recommended), or Reset to go back to the default.
2. Under Link preview, select Upload image to replace the image shown when the app's link is shared in Slack, Teams or on social media. Revert to auto-generated switches back. The auto-generated image is made from the app's name, never from a screenshot of your data.

Images can be up to 5 MB. Changes appear within a few minutes with no redeploy. If the panel says "Changes apply from this space's next deployment onwards.", the change takes effect after Viktor next deploys the app.

You can also ask Viktor to set the favicon for you.

Delete a Space

1. In Spaces, open the Space's menu and select Delete. Or open the Space, go to Settings, and select Delete space under Danger zone.
2. Confirm in Delete Space?. The dialog says the Space "will be removed from Spaces and scheduled for deletion. This cannot be undone."

Deleting removes the app's deployments and database. You can also ask Viktor to delete a Space. By default he confirms with you first, naming the app and saying that its data goes with it.

Limits

Who can do what

Other members see these settings read-only. For example, the Danger zone says "Only the space's creator or a workspace admin can delete this space."

Creating new Spaces

Creating new Spaces is rate-limited. Updating and redeploying an existing Space does not count toward this limit.

• A single-person workspace can create 10 Spaces per day and 30 per 30 days.
• Each additional member of your connected Slack workspace adds 2 per day and 6 per 30 days, counting up to 10 members (at most 28 per day and 84 per 30 days).
• Workspaces without a Slack member count, such as Microsoft Teams workspaces, stay at the single-person limit.

When you reach the limit, Viktor can't create the Space and tells you when you can try again. Reuse an existing Space instead of creating another one.

Deploys

Deploys are limited per hour and per day. The base is 15 deploys per hour and 30 per day. It is multiplied by the number of members in your connected Slack workspace (up to 10) and by your plan's level, with a combined maximum of 8 times the base (120 per hour, 240 per day):

When a deploy is refused and a higher plan would raise the limit, the message says so: "Upgrading the workspace plan raises this limit to N per …". Only one deploy of a Space can run at a time.

App emails

A Space sends its sign-up, sign-in code, verification and password-reset emails through Viktor, capped at 100 emails per hour per app. Past the cap, sends fail with "Rate limit exceeded" until the hour moves on. The cap can't be raised per app.

Credits

Spaces run on hosted infrastructure (database, hosting and compute) and use workspace credits based on each Space's resource usage. Workspace admins can see each Space's credit use under Usage at app.viktor.com/usage/spaces, or ask Viktor how many credits each Space used in a period. See how credits work.

Common problems

• Viktor says the Space limit is reached. Only creating new Spaces is limited. Ask Viktor to change an existing Space instead, or wait for the time the message gives.
• A deploy is refused as rate-limited. Wait for the window to pass. If the message mentions an upgrade, a higher plan raises the limit.
• "Another deploy of '{name}' is already running". Only one deploy of a Space runs at a time. Wait for it to finish, then ask again.
• Real data is missing from the app. You may be on the preview, which has its own database. Open the production URL (Open app).
• Sign-up or reset emails stop arriving. The app may have hit the 100-emails-per-hour cap. Wait an hour, and ask Viktor to add a cooldown to the app's resend button.
• You can't see the Database tab or the Delete button. Only the Space's creator and workspace admins can use them. Ask one of them.
• Create space is missing. It needs web chat to be available in your workspace. You can still ask Viktor in Slack or Teams.

Related

• Space access and domains
• Hosted pages
• Canvases
• Plans and credits
• How credits work