Mission Control user guide

Ostera Mission Control is a unified command dashboard for teams and organizations. It brings together the tools most teams juggle across separate apps - goals and OKRs, project and sprint planning, an issue tracker with a Kanban board, notes, chat, meetings, notifications, and attendance/analytics - into a single workspace scoped to your organization.

Everything in Mission Control belongs to an organization (your company or team). Inside an organization you create one or more projects (also called departments - e.g. Engineering, Marketing, Operations), each with its own members, board, and optionally its own sprints. Work is broken down into issues (epics, stories, tasks, bugs, subtasks) that move across a customizable board, and progress rolls up into goals so leadership can see how execution tracks against strategy.

This guide walks through the full lifecycle: setting up your organization, inviting your team, defining goals, creating projects, planning sprints, tracking work on the board, and using the collaboration and reporting tools around it.

Mission Control onboarding has three moving parts: a Super Admin creates the organization, team members join with the shared Organization ID, and the Super Admin approves each request (or adds members directly, skipping approval entirely). Roles then control what everyone can see and do.

1. 1
   Open the Ostera Mission Control sign-up page in your browser.
2. 2
   You will see three tabs at the top: Create Org, Join Org, and Join as Student. Select the "Create Org" tab.
3. 3
   Fill in the following fields:

   • Organization Name - Enter the name of your company or team (e.g., "Acme Corp")
   • Full Name - Your full name
   • Work Email - Your work email address
   • Password - Choose a strong password (minimum 8 characters)
4. 4
   Click the "Continue" button. A 6-digit verification code will be sent to your email.
5. 5
   Check your email inbox for the verification code from Ostera AI. If you don't see it within a minute, check your spam/junk folder.
6. 6
   Enter the 6-digit code on the verification screen and click "Verify email".
7. 7
   Once verified, you will see a success screen that says "Organization created!" along with your unique Organization ID (a UUID string).
8. 8
   Click the copy icon next to the Organization ID to copy it to your clipboard. Save this ID - you will need to share it with team members so they can join your organization.

   Organization ID

   a1b2c3d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d

   Copy
9. 9
   Click "Go to Dashboard" to enter your Mission Control workspace. You are now the Super Admin of your organization.

1. 10
   To invite team members, share the Organization ID you copied in Step 8 with them.
2. 11
   If you need to find your Organization ID again later:

   • Go to Settings → Organization from the sidebar.
   • Your Organization ID is displayed on this page with a copy button.
3. 12
   Share the Organization ID along with these instructions:

"Go to mission.ostera.ai/sign-up, select 'Join Org', paste this Organization ID, and fill in your details. Once submitted, I'll approve your request."

1. 13
   The team member opens the Ostera Mission Control sign-up page.
2. 14
   Select the "Join Org" tab at the top.
3. 15
   Fill in the following fields:

   • Organization ID - Paste the Organization ID shared by the Super Admin
   • Full Name - Their full name
   • Work Email - Their work email address
   • Password - Choose a strong password (minimum 8 characters)
4. 16
   Click "Continue". A 6-digit verification code will be sent to their email.
5. 17
   Enter the 6-digit code and click "Verify email". If the email hasn't arrived within a minute, check the spam/junk folder.
6. 18
   After verification, they will see a screen that says "Request sent!" - their account is now pending approval by the Super Admin.
7. 19
   If they try to sign in before approval, they will see an "Awaiting Approval" page with a message saying a Super Admin must approve their account.

1. 20
   As the Super Admin, go to Settings → Organization from the sidebar.
2. 21
   You will see a "Pending Approvals" section with a count of pending requests. Each entry shows the member's name and email.
3. 22
   For each pending member, you have two options:

   • Click Approve (green button) to grant them access to the organization.
   • Click Reject (grey button) to deny their request.
4. 23
   Once approved, the member can sign in and access the dashboard.

1. 24
   As a Super Admin, you can also add members directly without them going through the sign-up process. Go to Teams from the sidebar.
2. 25
   Click the "Add member" button (purple button, top right).
3. 26
   In the dialog that opens, fill in:

   • Full Name - The new member's name
   • Email - Their email address
   • Password - Set a temporary password for them
   • Workspace Role - Select their global role (see Roles & access levels below)
   • Project - Optionally assign them to a project/department
   • Project Role - Their role within the assigned project
4. 27
   Click "Add member" to create their account. Share the login credentials (email and temporary password) with them.
5. 28
   The new member can now sign in immediately - no approval needed.

Mission Control has the following Workspace (Global) Roles, from highest to lowest access:

Changing a member's workspace role

1. 30
   Go to Teams from the sidebar.
2. 31
   Find the member whose role you want to change.
3. 32
   Next to their name, you will see a role dropdown (e.g., showing "Member"). Click on it.
4. 33
   Select the new role from the dropdown:

   • Superadmin - Gives them full administrative access
   • Dept admin - Makes them an admin for their assigned departments
   • Member - Standard team member access
   • Viewer - Read-only access
5. 34
   The role is updated immediately. A "Role updated" confirmation will appear.

Managing project-level access

1. 35
   In the Teams page, under each member's name, you will see their project/department assignments displayed as chips/badges.
2. 36
   To add a member to a project: click the "+ Add to project" button below their name and select the project from the dropdown.
3. 37
   Each member can have a Project Role within each project they belong to. The project-level roles are:

   • Admin - Can manage the project settings and members within that project
   • Member - Can work on tasks, issues, and content within the project
   • Viewer - Read-only access to the project
4. 38
   To change a project role: click on the project badge/chip next to the member's name. A role selector will appear allowing you to change their role within that specific project.
5. 39
   To remove a member from a project: click the button on the project chip next to their name.

Additional Super Admin actions

1. 40
   Set/reset a member's password:In the Teams page, click the "Password" button next to any member to set a new password for them. This is useful for onboarding or if a member is locked out.
2. 41
   Remove a member from the workspace:Click the "Remove" button next to a member, then confirm by clicking "Confirm remove". This will remove them from the entire organization.
3. 42
   View a member's profile:Click the "Profile" button to view and edit a member's profile details.

The /route is Mission Control's home dashboard, and what it shows depends on your role:

• Members - A "Mission Day" panel to start/end your daily clock-in (see Attendance below), a "Your projects" card linking to every project you belong to, and a "Recent attendance" summary of your last 14 days.
• Department Admins - The same member view, plus a projects dashboard for the departments you administer, showing member counts for each.
• Superadmins - A full projects dashboard across every project in the organization (with the ability to create new ones) and an org-wide attendance overview.

The Goals page (OKRs) lets you set objectives at the company, project, or individual level, and track measurable key results underneath each one. Superadmins can always view and manage goals; other members need to be an admin of at least one project to create or edit goals. Members without manage access see a read-only view. Students only see and manage their own individual goals.

• Company - Org-wide objectives, visible to everyone.
• Project - Scoped to a specific project/department.
• Individual - A personal goal, owned by one person.

1. 1
   Open Goals from the sidebar and click "New objective".
2. 2
   Fill in the objective details:

   • Title - A short, outcome-focused statement of what you want to achieve.
   • Description - Optional context - why this goal matters.
   • Level - Company, Project, or (for students) Individual.
   • Project - Only shown when Level is "Project" - pick which project this goal belongs to.
   • Timeline - Choose "Period" (a quarter/half/full year, e.g. Q1 2026) or "Dates" (a custom start and end date).
3. 3
   Add one or more key results- click "Add key result" and give each one a short title. You need at least one.
4. 4
   Click "Create". The goal appears on the Goals board with all key results starting at 0% progress and status "On track".

Every key result has a current value, a target value, and a unit (e.g. 45% / 100%). Progress can be tracked in two ways:

• Manual updates - Anyone who can manage the goal clicks "Update progress manually" on a key result, enters a new current value, and saves.
• Linked to issues - Open any issue and set its "Goal" field to a key result. Once issues are linked, manual editing is disabled and progress is calculated automatically as linked issues marked Done ÷ total linked issues. The key result row expands (click the chevron) to show every linked issue.

Status is derived automatically from progress: Achieved at 100%+, On track at 70%+, At risk at 40%+, and Off track below that (a goal can also be marked Abandoned).

Editing, reordering & deleting

• Rename a key result inline by hovering it and clicking the pencil icon.
• Drag objectives, or key results within an objective, to reorder them.
• Edit a goal via the pencil icon on the objective - you can add, rename, or remove key results (removing one unlinks any issues attached to it).
• Delete a goal via the trash icon; you must type "Delete Goal" to confirm, since this permanently removes all its key results.

A project (also called a department) is a dedicated workspace for a team - its own board, backlog, members, and settings. Create one whenever you need to organize work for a distinct team or function.

1. 1
   Click "New project" (available from the sidebar or Teams page).
2. 2
   Fill in the "Spin up a new project" dialog:

   • Project name - Required. A URL-friendly slug (e.g. /d/engineering) is generated live as you type.
   • Accent - Pick a color used for the project's icon and highlights.
   • Project logo - Optional square image (JPEG/PNG/WebP/GIF, max 2MB).
   • Description - A short summary of what the project covers.
   • Template - Technology, Operations, Marketing, Finance, People, or Custom. Choosing a template pre-fills the accent color and pre-configures starter workflow columns, labels, and example issues.
   • Enable sprints - A toggle deciding whether this project plans work in sprints or runs as a plain board (see below). It defaults on only for the Technology template.
3. 3
   Click "Create project". You're taken straight to the new project's board.

The "Enable sprints" toggle set at creation (changeable later in project settings) decides how the project runs:

Each project has its own Settings page (Project Admins and Superadmins only) covering:

• Required fields - Toggle it on, then choose which fields must be filled before an issue can be saved: Assignee, Priority, Story points (with a configurable points limit, default 10), Start date, Due date.
• Rename project - Change the project's name and URL slug.
• Logo & accent - Update the project's icon image and accent color.
• Delete/archive project - Permanently remove or archive the project.

Only members added to a project can be assigned issues in it or see it on their sidebar (unless they're a Superadmin, who can see everything).

1. 1
   Open the project's Settings → Members panel.
2. 2
   Click "Invite" and choose an existing organization member to add to the project.
3. 3
   Set their project role:

Change a member's project role anytime from the same panel, or remove them from the project entirely (this doesn't remove them from the organization).

Each project has a Wiki tab for reference documentation - onboarding notes, processes, or team conventions specific to that project. Pages currently come from the project's template (a Technology project, for example, starts with a few pre-written pages); there is no in-app page editor yet, so treat the wiki as reference material seeded at project creation rather than a space your team edits day to day. For anything that needs regular editing, use Notes instead.

The Timeline tab is reserved for a future Gantt-style roadmap view - dependencies, milestones, and a "today" marker across your issues. It currently shows a "Coming soon" placeholder and isn't available to use yet. Until then, plan schedules using sprints, and issue start/due dates.

The History tab is a searchable log of every issue that has reached a "Done"-type status in the project - useful for looking up exactly what shipped and when, rather than for trend analysis (for charts and velocity, see Reports & analytics).

• Search & filter - Free-text search, plus filters for type, priority, status, assignee, parent epic, and a completed-date range.
• Columns shown - Issue key, title, assignee, story points, completion date, and parent epic.
• Paging - Choose 10, 25, 50, or 100 rows per page.

Available only in sprint-based projects. Sprints move through three states: Planned → Active → Completed.

1. 1
   On the project's Backlog page, click "New sprint" and fill in Sprint name, Start date, End date, and an optional Goal. It's created as "Planned".
2. 2
   When you're ready to run it, open the planned sprint and click "Start" (only available when no other sprint is currently active). Confirm the dates in the dialog to make it Active.
3. 3
   Add issues to the sprint either by checking issues in the backlog and clicking the "+N selected" button on the sprint header, or by dragging an issue onto the sprint.
4. 4
   Edit a sprint's name, dates, or goal anytime via "Edit sprint" on its header.
5. 5
   When the work is done, click "Complete sprint" to close it out. Any unfinished issues can be moved to the backlog or the next sprint.

Sprint Auto Mode

Turn on Sprint Auto Mode in project settings to have sprints automatically start/close on their dates. Choose what happens to unfinished issues when a sprint auto-closes: move them to the next sprint, or send them back to the backlog. With Auto Mode on, you'll also see a "Complete Early" option to close a sprint ahead of schedule.

The Backlog page is where work is drafted and organized before it enters a sprint (or the board, for non-sprint projects). It's split into two columns:

• Left column - Epics and unassigned issues. Use the "Filter by epic" dropdown to narrow the list to a specific epic or issues with no epic.
• Right column - Sprint planning (create/start/edit/complete, as above) and a "Key Results" tab for linking backlog issues straight to a goal.

Bulk actions

Check multiple issues to reveal a bulk action bar at the bottom of the screen: move all selected issues to a chosen sprint, or delete them (with a confirmation step). Individual issues also support quick actions: move to the board / To Do, add to a sprint, return to the backlog, assign or remove an epic, and delete.

An issue is the unit of work in Mission Control. Every issue has a type:

Today, the only structural relationship enforced in the product is issue-to-Epic: any Story, Task, Bug, or Subtask can be attached to an Epic via its "Epic" field, which groups related work together in the backlog and lets you filter by epic. Priority is set independently of type, from Lowest to Critical (Lowest, Low, Medium, High, Highest, Critical).

1. 1
   Click the "+" on any board column, or in the backlog, to instantly create a new issue (it starts as an untitled Task with Medium priority) - you're taken straight to its detail page.
2. 2
   On the issue detail page, set whatever fields you need:

   • Title & description - Click into the title field or the rich-text description editor to edit; changes save on blur/save.
   • Status - The workflow column it currently sits in.
   • Assignee & co-assignees - The primary owner, plus optional additional people via "Add co-assignee".
   • Priority & type - As described above.
   • Epic - Attach this issue to a parent Epic (non-epics only).
   • Goal - Link this issue to a key result so it contributes to that goal's progress.
   • Story points - A numeric estimate, capped by the project's configured limit (default 10).
   • Start & due dates - Plan when work begins and is due.
   • Attachments - Upload supporting files directly to the issue.
3. 3
   If the project has required fields enabled, a banner shows exactly which fields are still missing before the issue is considered complete.
4. 4
   Every issue gets a permanent key (e.g. TECH-142) shown on its detail page, and an activity log at the bottom records who created and last updated it.
5. 5
   Delete an issue from its detail page (with a confirmation step) if you have permission.

Only people added as members of a project appear in that project's Assignee dropdown - add them via the project's Members panel first (see Project members & access above).

• Primary assignee - Open the issue, click the Assignee field, and pick someone from the dropdown.
• Co-assignees - Click "Add co-assignee" to bring in additional people who share ownership of the issue.
• Reassigning - Simply reselect a different person from the Assignee dropdown at any time.

Every project has a Kanban board. Columns represent the project's workflow statuses and are fully customizable by project Admins:

• Rename a column - Click its header and edit the name.
• Reorder columns - Use the up/down controls on a column to move it left or right.
• Add a column - Click the "+" gap between two columns to insert a new status there.
• Delete a column - Remove a status you no longer need (its issues will need a new status).

Drag and drop any issue card between or within columns to change its status and ordering - this saves automatically.

Filtering the board

Use the filter bar above the board to narrow what you see by free-text Search, Assignee (including "Unassigned"), Type, Priority, or Epic. Filters are reflected in the page URL, so a filtered view can be bookmarked or shared with a teammate.

The My Tasks page brings together everything assigned to you (Work Tasks - issues assigned to you across every project) alongside your own Personal Tasks- a private to-do list that isn't tied to any project. Use the All / Work / Personal toggle to choose which list you see, and the tabs (All Active, Today, Due Tasks, Tomorrow, Next 7 Days, Completed) to filter both lists by the same timeframe.

Creating a personal task

1. 1
   Type into the "Add a personal task…" bar. As you type, Mission Control detects dates and reminders in plain language (e.g. "Call vendor tomorrow at 3pm") and shows a "Detected" chip you can Apply or dismiss.
2. 2
   Click the date/reminder button to open the scheduler - quick presets (Today, Tomorrow, Next week, Evening), a calendar, a time picker, a Reminder option (None, on time, 5–60 minutes before, 1 day before, or custom), and a Repeat option (Off, every 30 minutes, hourly, daily, weekly, monthly, or custom - repeating until the task is marked done).
3. 3
   Click the paperclip icon to attach one or more files - they upload once the task is created and can be added or removed later.
4. 4
   Press Enter (or click the Enter button) to create the task.

Managing a personal task

• Complete - Click the checkbox to mark it done (or undone).
• Attachments - A paperclip badge on the row shows the attachment count - click it to open a list of files (open, add more, or remove any of them).
• Edit - The pencil icon opens an edit dialog for the title, date, reminder, and repeat settings.
• Postpone - In the Overdue view, a calendar-clock icon lets you move a task to today, tomorrow, or a picked date - or postpone every overdue task at once.
• Delete - The trash icon removes the task immediately.

The older "Personal Inbox" link simply opens My Tasks with the Personal toggle pre-selected - it's the same feature.

The Activity page is an organization-wide feed, not just your own activity. It has three tabs:

• All - Every event, merged and sorted by time.
• Activity logs - Issue creation, updates, status changes, and epic changes - click any entry to jump to that issue.
• Mission logs - Clock-in/clock-out events across the organization (most recent 30).

Open chat from the round message button in the bottom-right corner of any page - it opens as a floating panel (a full-screen slide-up on mobile), with a maximize icon to expand it into a full modal. Inside, three tabs organize your conversations: Chats, Announcements, and Meetings.

• Direct messages - Search for a person under Chats and click their name to open (or start) a 1:1 conversation.
• Groups - Click "New group" and fill in a Group name, optional description, pick members to add, and optionally attach a project.
• Announcements - Click "New announcement" and set a Channel name and optional description. Every org member is automatically joined and only the creator can post. Creating an announcement channel is limited to Superadmins, and an organization can have at most 5.

• Sending - Type and press Enter to send; Shift+Enter for a new line. Drafts are saved automatically per conversation if you navigate away.
• Attachments & voice notes - Attach files (up to 25MB each) via the paperclip icon, or record a voice note with the mic icon - you can preview and re-record before sending. A separate dictation icon transcribes your speech into the text box instead.
• Reactions - Click the smiley icon on a message to react with an emoji.
• Replying - Click "Reply" on a message to quote it - the reply shows inline in the feed with a link back to the original.
• Editing & deleting - Your own messages can be edited or deleted from the message actions menu.
• Mentions - Type "@" in a group to mention a member, "@here" to notify active members, or "@everyone" to notify the whole channel (restricted to channel owners/admins, with a confirmation step).
• Linking work - Type "#" to search and attach an issue, or "/" to attach a project or a note - these render as rich cards in the message.
• Pinning & saving - Channel owners can pin important messages to a banner at the top of the chat; anyone can privately "Save" a message to find later.

From a DM or group's video icon (or the Meetings tab in the chat panel), you can start an Instant Meeting or a Scheduled Meeting.

• Instant Meeting - Give it a title, optionally invite people, and click "Start Meeting" to jump straight into the call as host.
• Scheduled Meeting - Set a Title, Description, optional Agenda, Date & Time, Duration (30–180 minutes), whether a camera is required, whether to enable a Waiting Room, and who to invite.
• Sharing a meeting - Use "Share Meeting" to copy the join link and passcode - anyone with the link can join, including guests without an account (they just enter their name).
• Waiting room - If enabled, guests wait until the host admits them one by one from a "Waiting Room" panel inside the call.
• In-call controls - Mute/unmute, camera on/off, screen share, and either "Leave meeting" or, for the host, "End for all".

Notes are a personal, rich-text workspace for documentation, meeting notes, or anything else worth writing down.

• Creating & organizing - Click "New note" to create one - it auto-saves as you type. Organize notes into folders, which can be nested inside other folders; drag notes or folders to move or reorder them.
• Formatting - The editor toolbar supports bold, italic, headings, text alignment, text color, highlight, and checklists. Insert images by dragging, pasting, or using the toolbar's Image button.
• Sharing - Click "Share" on a note, pick an organization member, and grant them "View" or "Edit" access. You can change or revoke access at any time; the recipient gets a notification and the note shows up under their "Shared with me" list.
• Searching notes - Use the dedicated "Search all notes…" modal inside the Notes workspace - this is separate from the global search described below.

Mission Control notifies you about time-sensitive and people-driven events:

Notifications respect quiet hours (9 PM–9 AM local time) and are de-duplicated so the same event won't repeatedly notify you. On the Notifications page you can click any item to open it and mark it read, use "Mark all read", switch to Select mode to mark specific items read, or "Clear all".

Push notifications

Enable browser push notifications via the permission banner shown in the app - this is an opt-in, per-device toggle (there's no separate granular preferences screen). Your subscription status is shown on the notifications page.

Press ⌘ + K (or Ctrl + K on Windows/Linux) anywhere in the app to open the command palette. Type to search across:

• Issues - By key or title.
• Projects - By name or slug.
• People - By name or email.

Before you type, the palette also shows quick actions (like "Create new project") and shortcuts to Mission Control, Goals, Teams, Analytics, and My Tasks. Notes aren't included here - use the notes workspace's own search instead.

Superadmins have access to an Analytics page with a "Project Performance Review" report, covering two views:

• Timeliness - Average completion percentage, share of sprints closed on time, total sprints run, best completion rate, and a score timeline chart, plus per-active-sprint completion projections compared to the previous sprint.
• Completion - Average completion ratio, count of "perfect" (100% done) sprints, percentage of sprints that closed with unfinished work, and average done-vs-total ratio.

Both views are backed by a sortable, filterable table of closed sprints - filter by date range, project, or status to drill into a specific team or period.

Time tracking is framed around your daily "mission":

1. 1
   On the Mission Control home page, use the Mission Day panel to pick which project you're working on.
2. 2
   Click "Start" to clock in - the panel shows "Mission in progress".
3. 3
   Click "End" when you're done for the day - the panel shows "Mission complete". You can't start twice or restart a completed day.

Admins and leads get a month calendar view at Attendance → Calendar, showing everyone's clock-in/out sessions with filters by user, project, date range, and status (completed/in-progress), plus an export-to-spreadsheet option.

Blockages aren't something you create directly - they're a live, auto-generated view (Superadmins only) of issues that need attention: anything sitting in a workflow column marked as a "Blocked" status, or anything still open in a sprint whose end date has already passed. The page shows summary counts (blocked/overdue, assigned, unassigned) and a filterable list with department, assignee, due date, and priority for each one.

• Resolving a blockage - There's no "resolve" button here - move the underlying issue out of its blocked status, or complete/reschedule it, and it drops off this list automatically.
• Sharing - Click "Share" on a blockage to post it into a chat conversation, so the right person can act on it.

Open your profile from the sidebar to update your avatar (upload and crop to a square), full name, job title, and timezone, then click "Save profile". Your email is shown but can't be changed here.

Viewing a teammate's profile shows the same details read-only. Superadmins additionally see a "Workspace access" section there to change that person's global role or activate/deactivate their account.

The Help page is a feedback form, not an FAQ - use it to report a bug, request a feature, flag a UI issue, or send general feedback straight to the team.

• Feature area - Optionally pick which part of the app your feedback relates to (Dashboard, Board/Sprint, Backlog, Teams & Members, Attendance, Personal Inbox, Notes, Goals/OKRs, Settings, Other).
• Type - Bug, Feature Request, UI Change, or General Feedback.
• Rating - An optional 5-star rating.
• Description - A required description of your experience or idea.
• Attachment - Optionally attach a screenshot or PDF (up to 10MB) to illustrate the issue.

For account or access problems specifically, your organization's Super Admin is usually the fastest route - see Roles & access levels above.

Org-level settings (Settings → Organization) cover your organization name, its creation date, the copyable Organization ID, and pending member approvals. Most day-to-day configuration - required fields, members, renaming, logo/accent, sprints - lives per-project under that project's own Settings page rather than centrally, so each team can configure its workspace independently.

• Set goals top-down - Start with company-level objectives, then let project admins create project-level goals that ladder up to them.
• Link key results to issues - Manual progress updates drift out of date; linking keeps goals honest automatically.
• Pick the right project type - Sprint-based for iterative delivery teams, non-sprint for continuous operational work.
• Turn on required fields - Especially Assignee and Priority - it keeps the backlog and board usable as the team grows.
• Use Epics to group work - Attach related Stories, Tasks, and Bugs to an Epic so progress can be tracked and filtered as a whole.
• Filter, don't scroll - Use board and backlog filters (assignee, epic, type, priority) instead of hunting through a long list.
• Review sprints regularly - Use the Completion and Timeliness reports after each sprint to catch scope or estimation problems early.

1. 1Super Admin creates organization → gets Org ID
2. 2Super Admin shares Org ID with team
3. 3Team members sign up with "Join Org" + Org ID
4. 4Team members verify email with OTP
5. 5Members land on "Pending Approval" state
6. 6Super Admin approves members in Settings → Organization
7. 7Approved members can sign in
8. 8Super Admin manages roles in Teams page
9. 9Super Admin assigns members to projects
10. 10Super Admin adjusts project-level roles as needed
11. 11Create company-level goals to set direction
12. 12Create a project, choosing sprint-based or non-sprint
13. 13Add members to the project with the right project role
14. 14(Sprint-based) plan the backlog, create epics, start a sprint
15. 15Create issues, set assignee/priority/estimate, link to a goal
16. 16Work issues across the board until Done
17. 17Track progress via Goals, Analytics, and Notifications

For any issues, contact your organization's Super Admin or reach out to Ostera support.