> ## Documentation Index
> Fetch the complete documentation index at: https://resources.athenaintel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Build for a client: build on Athena, publish, and let them sign in

> Athena gives consultants and forward deployed engineers a Computer, database, hosting, and company sign-in from day one so they can build with a client, publish the app, and let the client's staff sign in with their own work accounts.

> Athena gives you a Computer, a managed database, hosting, and company sign-in from day one, so you spend your time on the client's problem instead of setup. This guide shows you how to build a working app with the client, publish it, and let their staff sign in with their normal work accounts without needing Athena accounts.

## Why is setup the problem?

Forward deployed engineers sit with a business team to build software for a single problem. The build itself is meant to take days, and Athena lets you start on day one by providing the coding machine, database, hosting, and login integration that otherwise take longer to arrange than the actual coding.

The role started at Palantir and is spreading fast, with job postings rising more than 1,000% between January and August 2026 compared with a year earlier, [according to Lightcast data reported by Fortune](https://fortune.com/2026/09/03/forward-deployed-engineers-fast-growing-six-figure-silicon-valley-job-integrate-ai-with-customers-tech-careers-palantir/).

## What does Athena take off your list?

| Usually you would | On Athena |
| - | - |
| Set up a laptop to code on | Open a Computer with a terminal, files, and a live preview |
| Request a database | Create an Athena-managed database in your workspace |
| Find somewhere to host a demo | Share the Computer's preview link, then publish an Application |
| Connect the company login | Let viewers sign in through Athena or with the client's work accounts |
| Find a safe place for keys | Store them as Secrets that the app reads when it runs |
| Build something to run scheduled jobs | Use an Automation with retries and approvals |
| Set up an AI service | Hand AI tasks from the app to Athena's Agents (AI specialists) and AOPs (saved AI procedures) |

You focus on the work that requires judgment: understanding the process, deciding what to build, and checking the result.

## How does an engagement run?

1. Plan with the business owner using the interview in [Plan before you build](https://resources.athenaintel.com/docs/build-guides/spec-before-you-build.md), and agree on the test cases.
2. Build on a Computer with sample data while Athena writes the code following [the build standard](https://resources.athenaintel.com/docs/build-guides/build-standard.md), then share the preview in the same meeting.
3. Improve the app with the people who will use it, so they see each change as it happens.
4. Publish an Application to give the client a fixed link for review while you continue working on the Computer.
5. Run the test cases and get sign-off.
6. Let the client's staff sign in.

## How do the client's staff sign in?

![You build on a Computer with the client, then publish the app at a fixed link with saved versions. The client's team signs in with their own work accounts through the client's company login. Anyone at the client can sign in, and they see this app and nothing else.](https://mintcdn.com/athenaintelligence-e46bc9d3/U4e92C1IcbO5Ytjz/images/build-guides/forward-deployed-teams-1.webp?fit=max\&auto=format\&n=U4e92C1IcbO5Ytjz\&q=85\&s=67daedd4190c996a138be528cb056f3f)

Athena hosts the published Application in your workspace and lets the client's staff sign in with their own work accounts. You configure company sign-in in one of two ways:

* To let the client sign in with Microsoft work accounts, connect your workspace to Microsoft 365, ask the client's IT team for their organization's Microsoft ID (the Entra tenant ID, a unique identifier for their company directory), and enter it on the app.
* If your workspace has its own company login, use that instead. This approach fits a workspace set up for a single client.

Once sign-in is set up:

* Athena lets the client's staff sign in with their own work accounts without joining your workspace, and shows them only that app.
* Put team or group access rules inside the app itself, because Athena grants sign-in to anyone at the client's company rather than filtering by team or group.
* Your workspace members keep full access to open the app, improve it on the Computer, publish new versions, and roll back if a release goes wrong.

For a demo with no sensitive data, someone with edit access and admin rights (or an admin's permission) can make the link public. Your agreement with Athena sets the commercial terms for client access.

## How do I make it something the client can rely on?

* Follow the build standard and read Athena's report on it.
* Store records in the Athena-managed database, and keep only code in the files on the Computer.
* Add a health check so Athena tests each new version before it goes live.
* Turn sleep off if the client uses the app at all hours.
* Write a README as you go that explains what the app does, who owns it, and how to test it.
* Agree on who owns the app after you leave and who can roll it back.

## What to plan for

Athena keeps the app in your workspace and lets you transfer ownership to any other member of that workspace, so agree on who will take over before the engagement ends.

Line up the sign-in details early on both sides. Ask the client's IT team for their Entra tenant ID at the start of the project, and make sure you have edit access to the app plus admin rights (or an admin's permission) to let outside people in.

## Questions teams ask

> [accordion] Can the client's engineers take over the app?
>
> Yes. Invite them to the workspace that owns the app, and transfer ownership to them.

> [accordion] Can a person read the code?
>
> Yes. Athena writes normal source code in the framework you chose. Ask Athena to follow your conventions and write the README and design notes as it builds.

> [accordion] Can we build inside the client's own Athena?
>
> Yes. Athena can run in the client's cloud account or on their own servers, keeping the app, its data, and its users in the client's environment. See [deployment options](https://athenaintel.com/deployment-options/).

> [accordion] Does this work for internal projects too?
>
> Yes. Follow the same steps, and let your colleagues sign in through the workspace. See [From first draft to everyday use](https://resources.athenaintel.com/docs/build-guides/prototype-to-live.md).

> [card] [See it work](https://athenaintel.com/demo/)
>
> Thirty minutes, your workflow, and you leave with the work product.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.