Skip to main content
Solved

Obsidian integration permissions

  • February 27, 2026
  • 5 replies
  • 30 views

Forum|alt.badge.img+1

Our obsidian connector needs more permissions such as the ability to fetch audit log information to work. Is there a way I can edit the permissions of what this connector can do?

Best answer by Michael B

Got it.

There are two things that come to mind which could be causing you permission based issues when authorization the integration:

  • The `audit-log` APIs require `Enterprise-Shield`.  If your account does not have that add-on, permission granting will fail. See more information here
  • Only Account admins can grant the OAuth2 Account token. If your user is not an admin the grant will fail.

Let me know neither of these explanations fit what you are experienceing.

Comments

Leianne C
Forum|alt.badge.img+15
  • Lucid support team
  • March 2, 2026

Hi ​@imills, thank you for posting in the community! It looks like you are referring to this Obsidian Security integration from our Integration Marketplace - is this correct? This will help me take a closer look into your request. Thank you!


Forum|alt.badge.img+1
  • Author
  • March 2, 2026

Yes!


Michael B
Forum|alt.badge.img+4
  • Lucid product team
  • March 4, 2026

Hello imillis,

Since Obsidian Security builds and maintains that integration, I believe you will need to reach out to them for support. However, if your question is about how to enhance the integration itself and you have the access to do so, can you be more specific on what you are looking to enhance?

 


Forum|alt.badge.img+1
  • Author
  • March 4, 2026

Hello,

The issue is I am not able to adjust permissions in lucid to expand what it is sharing with obsidian, such as fetching audit logs like obsidian is requesting. Since obsidian is requesting it, it would be on lucid end to allow the adjustment of permissions to my belief. 


Michael B
Forum|alt.badge.img+4
  • Lucid product team
  • Answer
  • March 4, 2026

Got it.

There are two things that come to mind which could be causing you permission based issues when authorization the integration:

  • The `audit-log` APIs require `Enterprise-Shield`.  If your account does not have that add-on, permission granting will fail. See more information here
  • Only Account admins can grant the OAuth2 Account token. If your user is not an admin the grant will fail.

Let me know neither of these explanations fit what you are experienceing.