Choose what Ellie should use for screenshots during the App access step, the fifth of six steps on the GitHub path: Start, Connect, Your docs, Understand, App access, Write docs. This step is for anyone setting up a project from GitHub and deciding whether screenshots should come from a sandbox copy of the app, the live app, or be skipped for now. It exists only on the GitHub path. A project started from your website has no screenshots and no App access step.
Step 1: Open the App access step

Start from Set up your first help centre, then continue through the GitHub onboarding path until you reach App access, the fifth of six steps: Start, Connect, Your docs, Understand, App access, Write docs.
This step exists only on the GitHub path. A project started from your website has no screenshots and no App access step.
This step is headed Where should Ellie take screenshots? with the text In a safe sandbox copy of your app, or on your real, running app — your choice.
There are three cards to choose from. Run a sandbox copy for me (recommended) is selected by default.
Step 2: Choose where screenshots should come from
Pick one of these options:
Run a sandbox copy for me (recommended)
Choose Run a sandbox copy for me (recommended) if your app can be run from its source repository.
This option means Ellie runs an isolated copy of your app in a temporary cloud sandbox. Ellie clones your repository there, and a companion backend repository too if your app has one.
The card says: Ellie spins up an isolated copy of your app with its own test accounts and realistic example data. Your production app and real users are never touched — and you don't need to hand over any credentials.
With this option, these steps run:
- Setting up a test login
- Seeding example data
- Writing your docs
- Capturing screenshots
If Ellie found several user roles in your app, the card adds a message saying that Ellie will create a sandbox test account for each role so screenshots show every role's view.
Use my live app

Choose Use my live app if your app cannot easily be run from source, or if you want screenshots to show real data.
The card says: Ellie signs in to your running app and takes screenshots there. Strictly read-only: nothing is created, changed or deleted. Best when your app can't easily run from source, or your screenshots should show real data.
With this option, you enter:
- App URL
- Password
If Ellie found several roles, each role gets its own email and password row. Fill in the roles you want documented and leave the others blank. You must fill in at least one row.
Continue stays disabled until the URL is valid and every row you started has an email containing @ and a password.
The blue advice box explains that you should use an account with the plan, credits or quota needed to reach every feature you want documented. Ellie is read-only on your live app, so screens behind a paywall are skipped if the account cannot reach them.
In live mode, only Writing your docs and Capturing screenshots run. Nothing is provisioned or seeded.
The live-app login is saved with the project, is not shown back in the dashboard, is used for screenshot and crawl runs, and is deleted with the project. Ellie is instructed to browse read-only and typing into form fields is blocked.
Skip screenshots for now
Choose Skip screenshots for now if you want to finish onboarding without screenshots.
The card says: Docs are written without screenshots — articles show placeholders you can fill in later from the project page.
With this option, only Writing your docs runs.
Later, you can run Provision account, Seed data and Capture screenshots from Project → Overview, ask Ellie in chat to capture screenshots, or upload your own image in an article.
Step 3: Click Continue
When you are ready, click Continue.
While onboarding starts, the button shows Starting….
If starting fails, the wizard shows the server message or Could not start — please try again.
Step 4: Know what happens next
What happens next depends on the option you chose.
If you chose a sandbox copy
Ellie sets up a test login in the sandbox if needed.
- If the app has a signup form, Ellie fills it in and confirms it reached a logged-in state.
- For Supabase apps, Ellie gets an isolated Supabase backend in the sandbox.
- If the app has no self-serve signup but does have password login, Ellie creates account records directly in the sandbox copy of the database and proves they work by signing in through the real login form, with up to 3 attempts.
Ellie then creates realistic example data in the sandbox by clicking through your app so screenshots are not empty.
If you chose the live app
Ellie signs in to your running app and takes screenshots there.
Ellie's browsing is instructed to be strictly read-only, and typing into form fields is blocked while it navigates, opening existing records and tabs.
If you skipped screenshots
Ellie writes the docs without screenshots.
Articles show placeholders you can fill in later from the project page.
Good to know
- Can I change this choice later?
This choice is only made during onboarding at App access. There is no switch for it afterwards in project settings. A project that started from your website and connected GitHub later does not see this step. For sandbox tuning after onboarding, use Project → Settings → Automation → Sample data, Project → Settings → Automation → Simulated integrations, and Project → Settings → Advanced → Environment variables.
- Where can I see what was chosen?
In the project header, the chip reads Screenshots from a test copy or Screenshots from your live app. In the projects list, the chip reads Test copy or Live app.
- What if Ellie needs example data in the sandbox?
Ellie creates realistic example data in the sandbox by clicking through your app. You can guide this in Project → Settings → Automation → Sample data using Guidance for example data (optional). The guidance takes effect on the next seed run.
- What if I need connected screens captured in the sandbox?
In sandbox projects only, Project → Settings → Automation → Simulated integrations has an On/Off switch that controls whether Ellie fakes a connected third-party account so connected screens can be captured.
- What if a feature only appears when an environment variable is set?
In sandbox projects, set it in Project → Settings → Advanced → Environment variables. Variables are passed to the test copy only, never the live app, and apply from the next screenshot run or video. For step-by-step instructions, see Set environment variables for your test copy.
- What if Ellie cannot complete the sandbox sign-in?
If signup needs email verification, Project → Overview shows an amber alert: Ellie’s test sign-in needs verifying. If Ellie cannot get a working login, Project → Overview shows a red alert: Ellie couldn’t sign in to your app for screenshots. with the reason. These alerts do not stop setup. Articles are still written, and logged-out screenshots are still taken.
- What if a step takes too long?
Each background step has a time limit. If a step reaches its limit, it is stopped and you are told it timed out so onboarding does not hang, with a message to retry from the project page.
- My app only has Google sign-in. How can Ellie take screenshots?
Choose Run a sandbox copy for me (recommended). If your app has no self-serve signup (for example OAuth-only or invite-only registration) but does have a password login, Ellie creates account records directly in the sandbox copy of your database and proves them by signing in through the real login form, with up to 3 attempts. Apps with no sign-in at all are fine too.
- Can I use Google, GitHub or SSO sign-in with the live app option?
No. Use my live app takes an Email and Password only, so it needs an account that signs in with an email and password. If your app only has social or SSO sign-in, use the sandbox copy. If Ellie cannot get a working login, Project → Overview shows Ellie couldn’t sign in to your app for screenshots. with the reason. Articles are still written and logged-out screenshots are still taken, and you can upload your own signed-in screenshots later.