Endpoints to view, add and remove tools

[simon-20]

As a user,
I want to see, add, and remove which tools I have authorised for use
so that I can manage my organisation.

As a superadmin,
I want to be able to add and remove provider admin access to reporting orgs
so that I can help reporting orgs manage their systems without being delayed by needing to wait for developers.

Acceptance criteria

1. Functional Criteria Users should be able to view, add and remove tools the list of tools authorised for their organisation.

[simon-20]

@emmajclegg, which of a reporting organisation's users should be able to authorise and remove authorisation for a tool? Should this be restricted to ADMIN and EDITOR, or should CONTRIBUTORs also be able to do this?

[emmajclegg]

@simon-20 - I think it makes sense for org 'admins' and 'editors' to be able to grant/revoke provider admin permission on behalf of their organisation thanks (not 'contributors').

[emmajclegg]

To be implemented via #87

[simon-20]

@emmajclegg, GitHub closed this automatically because I've deployed it, but I'm reopening because I know you wanted to verify all completions before marking as done going forward.

[emmajclegg]

Thanks @simon-20 - this looks great.

Can I confirm what the drop-down options will be on IATI Account production? i.e. presumably no dev/local/staging versions of AidStream and Publisher?

Also - I'm not sure why "IATI Account Dev" appears in the authorised list for some test orgs and not others? If it's not relevant on production, don't worry.

Apart from that, I've tested the following and all looks good:

• superadmins, org admins and org editors can view + edit third-party permissions
• org contributors can view, but not edit permissions
• revoking then reauthorising permission works with no obvious errors in IATI Account
• proxying as a provider admin on IATI Publisher dev works as expected, according to the third-party permissions in IATI Account

[simon-20]

Yes, the list of 3rd party tools is specific to dev and production, so the list on production will contain only those tools defined on production, and there are only two: "IATI Publisher", and "Aidstream".

"IATI Account Dev" probably appears in some and not others because I've been using dev to do some testing, so was adding/removing that from various reporting orgs, as well as adding new reporting orgs to test with. So unrelated to production.

[emmajclegg]

Yes, the list of 3rd party tools is specific to dev and production, so the list on production will contain only those tools defined on production, and there are only two: "IATI Publisher", and "Aidstream".

Great - thanks for confirming @simon-20 . All looks good to go in that case.