The audit intake room.
Provided-by-client documents arrive through the portal. An AOP sorts, names, and matches them to procedures. The engagement team replaced a SharePoint-backed portal that clients called the "Uber tracker" for audits.
Give external clients a branded room to upload against checklists, check status, and ask questions—included in Athena services.
External clients use deployed portals without individual Athena licenses (see deployment terms).
Engagement teams still run intake over email and a SharePoint folder with a spreadsheet tracker. Clients cannot see what is missing. Reviewers cannot see what was read. Someone asks again.
Generic portals fix the upload and stop there: no agent, no status, no attribution.
Give the client a clear next step. Give the reviewer a decision.
Build the room. Describe it: what you need from the client, who reviews, what the brand looks like. Athena builds the Portal as an Application; you publish it to your custom URL (one-click promotion to your domain).
Invite guests. Through your IdP or a link. Each guest sees only their room.
Clients act. Upload against the checklist, comment, check status, ask the room agent what is outstanding.
Your reviewer decides. Only authorized reviewers record a decision. Read receipts, versions, and decisions are attributed. An Agent Operating Procedure (AOP) can sort, name, and match uploads to procedures before anyone opens them.
Apps. A full virtual machine per project with coding agents preinstalled. Describe an app, watch it get built, promote it to your people or your clients.
| Capability | People can | Agents can | Together |
|---|---|---|---|
| Apps | Describe it, review the preview and the code, promote it. | Write, test, and fix the code; ship new versions to staging. | Nothing reaches users until a person promotes it. Rollback is one click. |
Anything a person can do here, an agent can do with the same permissions, and both land in the same audit trail.
Provided-by-client documents arrive through the portal. An AOP sorts, names, and matches them to procedures. The engagement team replaced a SharePoint-backed portal that clients called the "Uber tracker" for audits.
Secure uploads, checklists, comments, and real-time matter status for a client's deal team. External clients use it, included in Athena services.
For clients who live in Slack, the same intake runs as a Slack agent: requests posted, files collected, status answered in channel.
Send the room contents to a diligence AOP (one-click forward) and get a cited first-draft memo back.
“It's good to understand the capability of the platform. That how far, and how quickly you guys can get these things going [...] that has been impressive overall.”
“Lets us get a lot more out of our data than [...] We can sit on top of all of the data in [our data warehouse] as opposed to just, like, our little ingested, you know, three gigabytes semantic models. I think we have a lot of power here.”
“Gave Athena the spreadsheet, explained which column I was trying to figure out, and then ten secs it told me... exactly how the calculation was based on the other data.”
“He wrote the entire stuff. By itself. And I was there, and I was thinking, alright. If I had to write all this stuff, I mean, I would've spent days, days, days.”
“I send that to the programmer and he said, alright. I read your file. I copied the section of the code because he has the right interface, and it works. Wow. Just like magic.”
“One workspace. All different, let's say, avatars of their output data. Right? Suddenly, it's dashboard. Excel is here. PowerPoint is when it's all together. It's very impressive.”
“Use the Athena platform probably closer to the concept and how it was designed, like, with the spaces architecture where you've got a set of primitives and capabilities, and you bring together the right set of capabilities to solve a task.”
“Digital worker, it gets spun up, it gets given access to the toolkits that it needs. It gets given access to the data that it needs. Just exists for the period it needs to exist to perform the task. And then it gets torn back down again afterwards.”
“I like that direction, that concept of the agent is the agent. It becomes an entity in its own right with its own ownership and its own missioning, and you get rid of the gray area and the blurry lines.”
“It was PowerPoint... there was no kind of distinction between the two. So that was killer. And I literally had a meeting on it today, and people said how great it was.”
Verbatim from customer calls. Customers anonymized.
Guests see only their room; permissions enforced per asset.
Only authorized reviewers record decisions.
Read receipts, versions, and decisions attributed and exportable.
Hard delete at end of engagement; discovery-aware retention controls.
Portals are for structured exchange. They are not a document management system and do not replace yours; iManage and SharePoint stay the system of record.
A secure, branded place for clients and partners to share documents and track requests.
They sign in as invited guests; access is included in Athena services.
A reviewer on your side, and every decision is recorded.
Records every change by a person or an agent, rolls back one contributor's edits without losing anyone else's, and keeps the model, instructions, and sources behind each agent action.
How the platform is deployed: Athena's managed cloud, your cloud on AWS, GCP, or Azure, on-prem, air-gapped, or GovCloud. Same platform in every option.
Build, Work, and Data on top; 150+ connectors and every surface in and out; one map of the whole platform.
We will build the room, invite a test guest, and show your reviewer the decision screen.