Skip to main content
Ellie inherits available workspace context, connected-source access, user permissions, and product configuration. It cannot make an unconnected system authoritative.

​
Permission checklist

  • The user belongs to the correct Entelligence workspace.
  • The connector is authenticated.
  • The repository, project, team, channel, or incident source is in scope.
  • User mapping is correct.
  • The destination connector permits the requested write.
  • A workspace administrator has approved write-capable use.
  • The user can verify and reverse the action.

​
Common issues

​
Action safety

Do not use Ellie to bypass:
  • Branch protection or required review
  • Incident command
  • Ticket approval policy
  • Finance or procurement controls
  • HR or employment-decision policy
  • Secret-management rules
When a requested action is ambiguous, ask Ellie to draft rather than execute.

​
Freshness

Ask which source and time range support an answer. Synchronization cadence differs across connectors and products. A recent source event may not appear until the connector or analysis refresh completes.

​
Escalate with useful evidence

Include the workspace, product surface, source, question with sensitive content redacted, timestamp, expected result, actual result, and source links. Never send credentials or raw private prompts in an unapproved support channel.

​
Next step

Return to the web quickstart or Slack quickstart after correcting access.