Skip to main content

Getting Started

Getting started with Worka should move you from an empty app to a workspace that is clearly taking shape.

You should not need to learn the entire platform before anything useful happens. The first run should make the product model obvious.

Before you begin​

You need two things:

  • a Worka account or an invitation to the right organisation
  • a clear description of the software you want

That is enough to begin. You do not need to connect every service up front.

Choose where you want to use Worka​

You can use Worka across desktop, mobile, and web.

For first-time setup, the most important thing is not the device type. It is whether you are signing into the right account and organisation, because that determines:

  • which workspaces you can open
  • which services and devices are available
  • which approvals and policies apply

Create your first workspace​

Once you are signed in, create a new workspace and describe what you want Worka to build.

At this stage, the best starting requests explain:

  • who the workspace is for
  • what it should help them do
  • which systems or sources matter
  • what the main view should make easy

If you are not sure how to phrase that well, read Create Software from a Goal.

What should happen next​

After you submit the request, Worka should begin showing visible progress.

You should expect to see some combination of:

  • a plan for the workspace
  • the first proposed views
  • AI team members or workflow activity
  • requests for service connections or approvals if they are genuinely needed
  • the first usable view appearing before every supporting view is complete

If nothing becomes visible and you are left in a blank space with no explanation, that is not a healthy first run.

When Worka asks for more access​

Sometimes Worka cannot continue without:

  • a service connection
  • approval for a sensitive action
  • consent to use a higher-risk capability such as browser control

Those requests should feel justified. You should be able to see what the workspace is trying to do and why the new access is needed.

If the request feels broad, vague, or early, stop and review before continuing.

Signs your first run is going well​

The first run is on the right track when:

  • you can tell what Worka thinks it is building
  • the main view looks sensible for the job
  • any requested connections or approvals make sense
  • the workspace shows progress rather than sitting in a vague loading state
  • the first delivered view is actually usable, not just visually present

Signs you should intervene​

Stop and redirect Worka if:

  • it is solving the wrong problem
  • it asks for access you did not expect
  • it proposes too many views for a simple job
  • the main view focuses on the wrong activity
  • it adds high-risk capabilities before you see why they are needed

If you intervene early, the workspace stays easier to shape.