Skip to main content

Community

Connector Improvement: Fine grained access control to re-sync at the connector level

Answered

Please sign in to leave a comment.

Comments

2 comments

  • Official comment
    Meera User

    Hi Jay, thank you for reaching out! We have this feature on our medium term roadmap. 

    I'd like to understand your requirements in a bit more detail. What's driving the need for one-off resyncs? Are there specific folks who should always be able to re-sync connectors? What are the roles & permissions of users who would need the one-off permissions? 

    Hi Meera,

    Thanks for considering this for the roadmap!

    Most of the time we don't need one-off resyncs, so we want to make it harder to make manual mistakes by revoking full refresh permissions at the connector and/or table level by default.

    We are planning to then invoke full refreshes via CLI commands on the fivetran API's in the rare case they are needed.  We need to enforce process some controls using CLI commands vs going through the UI.

    If we did need to do a refresh from the UI, we would want to enable the permission temporarily, start the refresh, then disable that permission once again.

    Hope this helps,

    Jay