Atlas is a project management and daily-accountability platform. Teams plan work on Kanban or Scrum boards, tie their daily updates to real ticket activity, run standups that start from facts already in the system, and give every role a clear view of what needs attention.
What you can do with Atlas
- Plan and track work on boards that use Kanban or Scrum, each with its own workflow stages.
- Break work into tickets (epics, stories, tasks, bugs and subtasks) with priorities, story points, due dates, attachments, comments and work logs.
- Run sprints from a prioritized backlog.
- Submit daily updates that can reuse the hours you logged on tickets, and present them in a standup.
- Schedule meetings, including recurring series with email reminders.
- Report on progress: hours, compliance and project health, exportable to Excel and PDF.
Roles
Everyone in an organization has exactly one role, the same in every project. Your role, together with each project's scope and team, decides what you can see and change.
| Role | Typical person | What they do |
|---|---|---|
| Admin | Owner, operations, engineering management | Runs the organization: users, invitations, roles, reporting lines, organization settings, billing, reports and the activity log. Has full access to every project, and alone can change a project's scope or manager. |
| Lead | Project manager, team lead | Creates projects, and sets up the projects they have full access to: details, team Members, boards and workflow stages. Runs the standup for the projects they can see. |
| Member | Engineer, designer, analyst | Works inside the projects they have full access to: tickets, sprints, comments, work logs, meetings and daily updates. |
Approving daily updates isn't tied to a role: your reporting manager (your Reports To person) approves yours. For the complete breakdown, see Roles at a glance.
How the pieces fit together
| Module | What it holds | Where to start |
|---|---|---|
| Projects | A client or internal initiative with a code (e.g. TS-004), a team and a scope (Private, Limited or Open). | Create a project |
| Boards | Each project has one or more boards. A board is Kanban or Scrum and has its own workflow. | Create a board |
| Tickets | Units of work on a board, numbered per project (e.g. TS-004-12). | Create tickets |
| Daily updates | One update per person, per project, per day: hours, what was done, blockers and the plan. | Submit an update |
| Meetings | One-off or recurring meetings attached to a project or board. | Schedule a meeting |
| Reports | Hours, compliance and health across projects, people and periods. | Reports basics |