Roles & permissions
inline uses a small, clear role model. Sign-in is through your Microsoft work account; what you can do once you’re in is governed by your role in the active organization.
# Signing in
Everyone authenticates with Microsoft Entra ID (your work account) — there are no separate inline passwords. Sessions refresh your role periodically, so a role change takes effect without needing to sign out and back in.
# Organization roles
Within an organization, each member holds one of three roles:
| Role | Can do |
|---|---|
| Owner | Everything an Admin can, plus rename the organization, manage members, and transfer ownership. There’s exactly one owner. |
| Admin | Manage connections, enable/configure repos, change review and module settings, approve learnings, manage notification channels, and view spend. |
| Member | Work within the organization — view reviews, findings, and dashboards, and interact with inline on PRs. |
Most day-to-day configuration is an Admin action. Anything that changes the shape of the organization itself is reserved to the Owner.
# The restricted developer role
Some people should only ever see their own work. inline has a confined developer role for that: a user restricted to a single /me view showing only the pull requests they authored, with no access to organization settings, other people’s reviews, or the broader portal.
A developer:
- signs in with their Microsoft account as usual,
- links their GitHub account so inline can match their authored PRs,
- can mint their own MCP keys for pre-PR review,
and nothing else. It’s the right role for a contractor or a large engineering org where most developers just want inline’s feedback on their own PRs without the administrative surface.
The role is assigned through invites: invite someone as a confined member and they land in the developer view.
# Linking a GitHub account
Linking is about identity, not access — it tells inline which GitHub login is you, so it can attribute your PRs, and (for developers) scope the /me view. It never grants inline new repository permissions; those come only from the organization’s GitHub connection.