An Administrator can create or manage tenants

[armahillo]

A superuser / administrator can perform CRUD tasks on tenants (spinning up new instances, managing existing ones, etc)

[abachman]

this may be a separate Admin model, since they'll be managing users but not creating donations, for example.

[seanmarcia]

@abachman @armahillo
I wonder if we need an Admin model or just an admin or super_admin attribute on the user model? This is my gut feel as I imagine that Rachel and people she picks will ultimately be the ones administering this. So she'll need to create donations, distributions and all the regular stuff as well as doing the admin stuff.

I wasn't in the room so I don't know the flow of how you all envisioned the flow but in my head it goes something like this:
Users who are super admins have a manage organizations dropdown menu.
It contains:
View Organizations (index page)
Create Organization (Create)

After creating the organization it goes to the show page. The show page lists all the users (if any) associated with the organization. It also as a button "Invite User to Organization" that takes advantage of the devise invitable to add users to that organization.

[cattywampus]

I think I agree with @seanmarcia. From a workflow perspective, this seems like a new hat that someone who already has access to the system would wear, on top of their existing responsibilities. Those with admin privileges would just have the ability to manage those orgs and send out invitations for others to join those organizations.

From an implementation perspective, a separate model in Devise is a separate login session. So switching those hats would require logging off as the org owner and logging in as the diaper base administrator.

[armahillo]

Unless the model for the admin user is going to be very different functionally, I'm good with just doing a field attribute -- that seems simplest. We can refactor into STI or something later if necessary.

[armahillo]

Fixed by #104