DocsApplicationsOrbit
Loading documentation, please wait.
NEMORIONDocsOrbit brings planning, work items, discussions, and documentation into an application your organization can host on its own infrastructure.
It is designed for teams whose need to collaborate comes with limits on who may see the work. Security boundaries should remain meaningful while people organize projects, contribute knowledge, and get things done.
Tasks have owners, dependencies, discussions, and decisions behind them. Orbit gives related work and documentation a shared home so people can follow the context they are authorized to see.
Labels and custom fields provide additional ways to organize work and capture the details your team needs.
Spans are time-boxed planning intervals: a sprint, an iteration, or another defined period in which a team plans and reviews work.
Each workspace can define its own work item types. A team can organize larger efforts as Programs or Initiatives and track individual pieces of work as Tasks, Bugs, Defects, or other types that fit its process.
Workspaces can also create and manage their own statuses. A software team's review process and an operations team's approval process can use different stages, with names that make sense to the people doing the work.
Settings cascade from the tenant to its workspaces where inheritance applies. Tenant administrators can establish shared settings and leave room for workspace customization, or lock them so workspaces must follow the configuration.
For example, a company that needs consistent statuses for reporting can define those statuses at the tenant level and lock them. Workspaces then use the same statuses, keeping the reporting vocabulary consistent across workspaces.
This supports both local flexibility and company-wide standards. The cascade is part of the shared platform settings model. Individual settings support inheritance and locking where those controls apply.
Different participants may need different parts of the same effort. An assignee can receive access to an individual task without that assignment opening the larger initiative.
Documents have separate permissions for discovering, reading, commenting, editing, and sharing. Folder isolation allows a document audience to be separated from the surrounding workspace.
These controls support collaboration with a deliberately limited audience. Broad grants and inherited permissions are now available as part of the access decision, but are not required.
Read about security and compartmentalization
Managing a workspace does not automatically make someone a reader or editor of its contents. Management and content permissions are distinct, allowing an organization to assign those responsibilities separately.
Permission to administer access is still powerful. Your access policy should account for who may grant additional permissions as well as who can read information today.
Orbit's core purpose is managing work. A team does not need an AI assistant to plan a sprint, milestone, or project. Nor to maintain documentation or collaborate on tasks.
Controlled AI access is an additional direction for interacting with that work. Permission-aware retrieval and clear attribution are the relevant principles. An assistant acting on a person's behalf should respect that person's information boundaries.
Orbit is in alpha and is the initial destination for managed onboarding. The local self-hosting guide is coming soon.