Removing an Organization User

In This Lesson

We'll add the ability to remove users, including ourselves, from an organization. We'll also discuss a few key elements needed to handle this gracefully.

Created by: @tomgobich
Published: 1 year ago

Join the Discussion 0 comments

Be the first to comment!

Transcript

So now the last feature that we have to tackle for our organization settings page is the ability to remove an organization member.
So let's go ahead and jump back into our terminal here and start yet again by making our actions. So node ace make action, put this inside of our organizations folder
and call it remove organization user. Okay, we can clear that out, jump back into our text editor and let's go ahead and dive into that action. So remove organization user and we're gonna want two different things here.
The organization of type organization as always. And we're also gonna want the user ID that we actually want to remove out of this organization. And so that we take all possibility of confusion out of the equation,
let's go ahead and call that remove user ID and give it a type of number. Within our handle method, we can go ahead and grab the organization as well as that remove user ID.
And how difficult you wanna get with this actual operation is completely up to you. If you just want to await organization related users
and detach the desired removed user from this organization and call it a day, what would be a little bit more of a catch all situation for this though, is if we treated this a little bit more
like our account deletion action. So for example, if we jump back into our destroy user account action, we have this delete dangling organizations, where it takes in the user and it checks for organizations
where that user is the only member and then deletes them out if any are found. So in the case of our remove organization user, we could use the same premise just a little bit differently.
We could check to see whether or not this specific organization only has this specific user inside of it. And if it does, then we can go ahead and delete that organization as well. And that would also allow for any user
to be able to safely remove themselves out of the organization. Then if it's just the last person removing themselves, we just delete it out of the database. So before we actually detach the user,
let's go ahead and get an other user out from our organization. So we'll use our organization, reach for the related users.
And then we can query with this. I'm gonna give myself a couple of line breaks to work with here. And then we wanna do where not the ID is the remove user ID.
And then we can go ahead and count them up by their IDs. Give that a save to format it and then we'll walk through what we have here. So for the specific organization that we're wanting to remove this user from,
we're reaching through that organization to its users and counting them up by their IDs. Then we're removing from that count the specific user that we're looking to remove.
So we know that if our other user count is zero, then the removed user is the only user inside of the organization. And we can go ahead and delete it out.
Now, of course, remember we are dealing with models here. So the other user count is not going to actually be our count, but rather our user model array.
So let's also tack on here a first or fail. Since we're doing a count, it will just come back with a user model with our extras populated. And then we can go ahead and wrap this in a transaction.
So await DB transaction async, get our transaction here set up, move our detach into that transaction.
And then where we actually delete the organization doesn't really matter because the detachment here from the user would go ahead and cascade with the organization's deletion.
But we'll go ahead and do it after the detach. If other user count dot, and we want to reach through the extras. And I want to say that's going to come through as count,
but I'm not 100% sure I am remembering that correctly. So I'll tell you what, let's jump into a REPL session real quick. Node Ace REPL, let's await load models.
And let's go ahead and grab our organization as await models organization. And let's find by or fail the organization name
where it is my second organization. So my second organization, run that. And we should have now our organization populated.
And now we can go ahead and do awaits, which through our organizations related users, query from there. And all I really care about is what this property is called.
So I'm just going to go ahead and run a count and let's plop this into user counts. All right, hit enter there to run it. And okay, the ID is ambiguous between our organization and users.
So let's hack on our users ID within our count, run that. And now user counts already defined.
All right, let's just switch that name there to count. Run that, there we go. Now we have our count. We can reach to the first index, which is where our actual count will be.
And then reach through to the extras object. Yeah, okay, so we have count of four. And you'll notice that it's a string. So that's what we're going to be working with right here
where we have our extras count. So we can either turn that into a number and do a greater than check, or we can just see whether or not it equals zero. If it equals zero, then we know that we're okay to go ahead
and delete the organization because that means that this removed user is the one and only user from that organization. So at that point we can await organization and just call the delete method.
Before we call this done and dusted though, we actually need to rig our transaction up to these operations. And since the detachment goes through our organization, and then we just delete the organization itself,
the only thing that we need to bind the transaction to is our organization. So we'll say to use the transaction here off of our organization, just like so.
And now we can call this action done and dusted. Let's jump back into our organization controller within our settings, because we now need to fill out our remove user method.
So for this, we'll have our response, the organization, programs, and session from our HTTP context.
We can go ahead and await remove organization user, call the handle method, pass that organization on in. And then we also have our remove user ID,
which will come from our programs ID. Once we have removed the user, we can go ahead and session/success, member has been successfully removed,
and then return response redirect on back. Now you might be wondering what about the use case where the organization is actually deleted within this action?
Do we indeed actually just want to redirect them back like nothing happened? And the answer is, yeah, we can. We set up our organization middleware so that we'll successfully check and see whether or not the organization's there,
and then load in another organization that the user is bound to if it is not. And then in addition to that, it will also redirect them back to the create organization page
if the user is not bound to any organization at all. So in the case where the user is removing themself from the organization and they are the one and only user inside of the organization,
our system via our organization middleware is rigged up okay to handle that successfully. So let's jump now back into our organization users card,
where we have just like in the last lesson, our empty table cell here to fill out a inertia link with our action to remove the user. Go ahead and end that link out,
and break this down into new lines, and we can rig up the actual href and point that to /settings/organization user,
and then plop the member ID of the member that we are currently looping over right up here in our table row. Okay, then this is a destructive action.
So we'll set the method to delete. We also need to set the route up. I almost forgot about that. So we'll do that here momentarily. Last text read 500, and then of course,
reserve that scroll position just in case the user is not deleting themselves, which is most likely going to be the case. All right, now just like in the last lesson, I also forgot the as prop here as well. So we'll add in our as button
so that this is rendered out as a button element rather than an anchor element. All right, we can give that a save, and then let's jump back into our web routes so that we can rig this route up.
So router, we'll have another delete here pointing to our settings, organization, user, and then tack the user ID on there.
I have this go to settings, organizations, controller, and bind it to our remove user method. As, settings, organization, user, remove.
There we go. Okay, with all that set, let's jump back over into our browser now. And there we go. We can immediately see our remove buttons across everybody. And let's go ahead and try to remove test invite three.
So let's click remove right there. And ran into that issue within our REPL, but I completely forgot to account for it inside of our actions. Let's jump back down
into a remove organization user action. See, where is this? Right here, where we have our count. Again, the ID column that we're counting by is ambiguous between our organization
and the users that is joining in. So we need to specify that this is from our users table there. But in this case, we also have the users being referenced on our where not there as well.
So we also want to update it there too. So let's tack our users.id on there so that both of those know which table we're referencing the ID column off of within that join.
Okay, give that a save. Now we can jump back into our browser. Let's go and get rid of that pop-up. I'm gonna give this a sanity refresh here. We can jump back down, click remove. There we go.
Member has been successfully removed and we see them out of our organization members now. Let's go ahead and jump over to one of these other organizations that we have set up. We'll do my fourth,
we'll jump down to the last one here in the list and jump over into the organization settings within here, where we are confirmed to be the only user inside of this organization.
Let's go ahead and try to remove ourselves. And there we go. Member has been successfully removed. And in addition to that, we are now switched back over to my second organization
and my fourth organization is removed out of our organizations list. And it should have been removed out of our database altogether.
So if we go ahead and I'm gonna exit out of here, clear that out, node ace, REPL await load models and await models organization,
find by the name my fourth organization, we get back null as our result. So it indeed did not find it in the database there either.

Building with AdonisJS & Inertia

91 Lessons

14h 3m

Getting Started

The Basics

Working with Forms

Database & Project Scaffolding

Authentication & Onboarding

The User's Organizations

Difficulties, Statuses, & Access Levels

Courses

Modules & Lessons

Settings

Organization Members

Authorization

InertiaJS 2

Stop losing your best ideas!

Use our integrated note feature to capture and organize your key insights. Take a note at any timestamp and jump instantly back to that moment in the video with a single click.