Instead of controlling the built in permissions.

I want to look at creating custom permissions and

applying them to users and views, because the workflows the same,

as far as the application, like must have this permission.

But creating custom permissions is the more interesting thing to do.

So the community member model.

If you remember this one has this concept of roles.

So right now there are four roles.

There's band, member, moderator or admin.

I think there should be a permission that community members have

before they can ban someone, right?

They should be able to ban abusive members definitely, but I might want,

maybe there's a trusted user who should be able to ban users but they

shouldn't be able to do whatever moderator abilities I give to everyone else.

Or maybe I wanna give ban user to both moderators and admins.

But moderators have one group, admins have another.

I don't wanna have to implement both of those in view logic.

So, I'm gonna create a ban member permission

that I can then give to whomever I need to give it to.

So down here in the class Meta, not there,

I'm gonna add a new attribute which is named permissions and

it's a tuple, and it's a tuple of tuples, and this tuple has two items.

It has ban member which is the short name, the code name.

And, then it has a longer name, can ban members.

And this longer name is what gets displayed in the admin.

You can make this longer.

You can put in whatever description you want here.

I try to keep it short and

sweet though because it's displayed in a fairly small little thing.

So it's not necessarily the thing that you want to make really long.

Okay so when you add a permission you are actually adding a thing to

the permissions table which means that you need a migration.

So let's go ahead and make this migration manage.py makemigrations for communities.

And you'll see that we change the meta options here.

So Pythonmanage.pie migrate communities.

Let's just migrate period, okay.

So now it's done that and

I can just run the server again to make things easier for me later on.

Before I go too far though,

I actually want to add a few handy properties up here to my community model.

So that I can get a list of admin and moderator uses.

So the first one I'm gonna add, so these are all gonna be properties.

So @property def admins.

And I'm gonna return self.members, or

memberships rather, .filter, where the role is equal to 3.

And I want to return the values list of user and I want flat to be true.

So this is going to return me a list of the ID's

of the users that are admins and then I'll make

another property here which will be moderators and

this is going to be very similar self.memberships.filter

role equals 2 and again user and flat.

So just returning a list of ID's.

The last one is a little bit different.

This one's gonna be called good members and

this is gonna hold all the members who are currently in good standing.

So self.memberships.exclude role equals 0 so

don't include anyone who is banned but other than that.

Send me back everybody.

Okay.

These could maybe should even be done as methods

on a custom model manager that however is outside the scope of this course.

And honestly it's something I bet you can all handle.

At this point on your own you've seen a lot of stuff you've seen how to do custom

managers on the user model.

I bet you can figure this out.

If not though, check the teacher's notes.

I'm going to link to docs on how to do custom model managers

with methods like this for quickly getting a query together.

All right so now though I'm here in the admin and I'm gonna create the moderator

group that I want to use some I'm gonna click add next to groups.

And I'm gonna create a group named moderators and if I look here in

the filter if I search for ban I see this, communities can ban members.

So that's one I want them to have.

So I'm just gonna hit save on that.

And all right, cool.

So, now I need to check for

the permission before I show any ban buttons or anything like that.

I'm gonna add a great big snippet of html to the template and

we'll talk about some of it.

But you should check the teachers notes, or not teacher notes, sorry, you should

check the workspace, the downloads, all that stuff to see what's going on here.

Cuz it's a large template and

going through it line by line is just going to take a long time.

So copy that.

Paste it into there.

So let's look through this.

It's a new card, it's called members.

And for

every member who's in the good members I'm gonna print out a link to their page.

So you can quickly jump and see all of their posts.

Then there's a new column here on the other side, and

if the user who's requesting this.

So the requesting user is an admin or

a moderator then we're gonna do this other stuff.

So if they're moderator then we're gonna show this.

If the user that we're currently looking at is a moderator then we're

gonna show this thumbs down here so that they can be downgraded to a regular user.

If they're not a moderator and they're not an admin, then we're going to show

a thumbs up icon here that will upgrade them to a status of 2.

So we'll promote them to being a moderator.

And regardless of that, the person who's looking at this

if they have the ban_member permission from communities and

perms is a little thing that gets inserted.

How we have, how you have user,

perms is another one that gets added in that same section

that holds all the permissions for the current user who's requesting the page.

So if perms.communities.ban_member exists which means they have the ban

member permission, then we're gonna show this ban circle icon and

we're gonna give them the ability to set somebody's status to 0.

So somebody can be banned.

Now you see that this is using this communities change status URL,

which doesn't exist yet.

So I need to make that exist, right.

View doesn't do any good or

sorry the buttons only good without the view to handle all that.

So the first thing I need to do is create the URL, and

this is it's a big URL, so buckle up.

I'm gonna do change status.

And then I'm gonna get a slug.

And so this slug is the slug of the community that the member belongs to.

And then I'm gonna get a user ID which is going to be one or more, the ID.

I should probably use username here but user id is fine.

And then I'm gonna get the status that they want to be changed to.

And this is only a single digit at this point.

If you end up building this and you have ten plus statuses,

you may want to change the status to be more than one digit.

Or maybe it becomes a word or something like that.

And this is gonna go to change status.as view,

which doesn't exist yet and I'm gonna name this change status.

All right, so capture the slug, capture the user id,

capture the status that we want them to become.

And yeah it's not the friendliest URL ever, but it's not a terrible one.