I've noticed this experience when helping on user's websites. They are obviously using their own Asana information for the frontend, yet I still need to put in my Asana PAT for my WordPress user to even access unrelated settings such as Asana Data Cache. It's not a huge deal for me personally, but I can imagine it being problematic for third-party agencies, consultants, or developers trying to work on client's sites with Completionist.
I've noticed this experience when helping on user's websites. They are obviously using their own Asana information for the frontend, yet I still need to put in my Asana PAT for my WordPress user to even access unrelated settings such as Asana Data Cache. It's not a huge deal for me personally, but I can imagine it being problematic for third-party agencies, consultants, or developers trying to work on client's sites with Completionist.
When we overhaul the settings admin page experience, we definitely need to consider a single-page experience which separates plugin settings vs Asana account-related settings.