Campaign Managers (EPIC)

[stevejgordon]

Initial stub issue around requirement for more granular authorisation levels for allReady after discussions with @schuback

Campaign Managers should be able to perform the following actions within the scope of a specific campaign

• view campaign admin page
• create events - pending new auth classes
• create tasks - pending new auth classes
• create itineraries - pending new auth classes
• create manual requests - pending new auth classes
• edit campaign details - pending new auth classes
• close out requests - pending new auth classes
• send messaging to all campaign levels - pending on updated messaging flow
• Update campaign lister / add a new lister page where a campaign manager can see links to campaign(s) they have access to manage - Included in Campaign Managers can view list of Managed Campaigns #1894
• Update menu rules so that anyone with campaign manager access has an admin menu with a link to the admin campaign list - Included in Campaign Manager Admin Menu #1895

A user will be invited by an org admin to become a campaign admin - see #1804

We will need to include a way or storing details of which users are campaign managers in our database. We will also need to include some changes within our authorisation code to ensure we allow the correct access to campaigns for the user's who should have it.

• Include a page which will lists all authorized campaign users - i.e. org admins and campaign managers - Included in Campaign Access Lister #1896
• Add a button with a confirmation screen to allow an org admin to revoke campaign manager access from a user - Included in Revoke Campaign Manager Acccess #1897

[stevejgordon]

Working on a PR to enable easier authorization logic to support this "role"

[oneolddev]

I'm going to take this one if no one minds. I've got a lot practice with #1803.

[oneolddev]

@stevejgordon @tonysurma

I've got the enable campaign manager part done but it's dependent on #1970. I'll create a PR once #1970 is merged.

@stevejgordon In making these changes, it feels like there should be an IAuthorizableOrganization interface with associated support classes for consistency purposes. I ended applying an [Authorize("OrgAdmin")] attribute to some methods. Thoughts?

[stevejgordon]

it feels like there should be an IAuthorizableOrganizationinterface with associated support classes for consistency purposes

@c0g1t8 Yep, that's my thought too. It makes sense to have a standard approach.

[oneolddev]

@stevejgordon I'll take a crack at IAuthorizableOrganization