> For the complete documentation index, see [llms.txt](https://docs.aethra.work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aethra.work/feature-scope-mvp/mvp-feature-set.md).

# MVP Feature Set

AETHRA’s initial public release delivers a streamlined core feature set designed to solve immediate workforce management pain points while laying the foundation for rapid iteration.

## Core MVP Features

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Bulk Employee Import</strong></td><td>Easily upload employee rosters via CSV or Excel to onboard hundreds of professionals in seconds.</td></tr><tr><td><strong>Multi-Account Organization Support</strong></td><td>Create and manage multiple sub-accounts under a single organization. Ideal for department-level access and control.</td></tr><tr><td><strong>Employee Portal &#x26; Shift Assignments</strong></td><td>Each employee receives a secure login to view their profile, credentials, and upcoming shifts.</td></tr><tr><td><strong>Shift Acceptance &#x26; Rejection</strong></td><td>Workers can accept or decline shift invitations directly in the portal, improving visibility and scheduling accuracy.</td></tr><tr><td><strong>Continuous Feature Cadence</strong></td><td>After MVP launch, AETHRA will ship updates every 6–8 weeks with features prioritized based on pilot feedback and community input.</td></tr><tr><td><h3><img src="https://content.gitbook.com/content/T0YJEubtYKsyCaLN2xfB/blobs/xxDdSEcuemrk9ZotvfHx/Subtract.png" alt="" data-size="line"> What’s Coming Next?</h3></td><td>Advanced analytics, credential visualization, mobile optimization, and role-based access controls are already in development and will ship in future updates.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aethra.work/feature-scope-mvp/mvp-feature-set.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.