Managing service members

Imagine you opened member login on "Cozy Closet," your online clothing store, and shoppers started signing up one by one with their social accounts. From here on, you have members to keep an eye on. That means checking the roster of who signed up, approving sign-ups one at a time, giving your premium members broader permissions, and keeping out members who only post nonsense.

This page covers, situation by situation, how to run and manage members who have already signed up (ServiceUser, a shopper who signed up for your service directly). It walks through checking the roster, approving new sign-ups, blocking a login, adjusting a specific member's permissions, and granting the permission to clean up other members' posts, in that order.

Two boundaries are worth drawing. First, the members covered here are the shoppers who signed up for your service, not the operators (the team) who register products and manage the site. Inviting and managing that team is covered in Inviting Members and Granting Permissions. Second, this page is about running a member login you have already turned on. Turning on member login for the first time and connecting social login is covered in Service Member Login, and creating the permission bundle to grant members is covered in Member Roles and Permissions.

Where the member roster lives

You view signed-up members by expanding Services in the left menu, going into ServiceLogin, and then opening Users. Every time a shopper signs up, one more entry piles up in this list.

The list shows one member per row across four columns.

• User: the name and email. A member whose Login allowed toggle is off gets an INACTIVE badge next to their name, and a member who can clean up other members' posts gets an Admin badge next to their name.
• Provider: the kind of social login the member used to sign up. It shows as an icon, such as Google or GitLab.
• Role: the permissions (Role) applied to that member.
• Joined: the date the member signed up.

1. In the left menu, expand Services and click ServiceLogin.
2. Click Users.

To see a member's details or change their settings, click the ∨ (expand) at the far-right end of that row. Instead of moving to another screen, the Permissions and Account details expand right below that row.

As members grow and the list gets long, you can narrow it down to just the members you want with the Role filter and the Status filter above the list.

Approving new sign-ups

If you turned on Require admin approval for new sign-ups in the member login settings, a newly signed-up member cannot log in right away and waits for an operator's approval. This is the approach to use when you do not want to let just anyone in immediately, but would rather check once and then accept them.

In that case, the new member appears in the list with an INACTIVE badge. When you expand that member's row, turn on Login allowed in the Account section, and save, the member can log in with their own account from that point on, and the INACTIVE badge disappears from the list.

1. In the Users list, click the ∨ (expand) on the row of the member waiting for approval (the one with the INACTIVE badge).
2. In the Account section, turn on Login allowed.
3. Click Save.

To accept new shoppers right away without checking them one by one, leave Require admin approval for new sign-ups off. How to turn this option on and off is covered in Service Member Login. Turning the option off does not automatically pass members who were already waiting for approval, so allow each waiting member with the method above.

Blocking a problem member's login

If a member only posts nonsense or harms other shoppers, you can block that member's login. You do this by turning off the Login allowed you switched on when you approved them. Once you block the login, that member can no longer get in with their own account, and they show in the list with an INACTIVE badge.

1. In the Users list, click the ∨ (expand) on the row of the member you want to block.
2. In the Account section, turn off Login allowed.
3. Click Save.

Blocking the login leaves that member's record and everything they left behind untouched. Turn the login back on and the member can get in again as before. This works well for blocking a member for a while and then bringing them back.

The content studio has no feature to erase a signed-up member entirely from the roster. To keep a member out, you block them by turning off Login allowed, not by deleting them.

Giving a specific member different permissions

Every newly signed-up member gets the same permissions, namely the Default Role from the member login settings. But there are times when you want to give only some members different permissions. Maybe you want to give a long-standing premium member broader permissions, or let a specific member use a new feature ahead of everyone else. In that case, you assign a different Role to that one member alone. Permissions assigned this way, per member, take priority over the Default Role.

Here is how it plays out for the clothing store.

• What goes in (the default setup): every member gets "Regular Member" as their Default Role. This permission lets them read reviews, write new ones, and edit only their own reviews.
• What you do in the content studio: for just one premium member, "Olivia," you assign the "Premium Member" Role separately.
• What comes out: "Olivia" now operates with "Premium Member" permissions, while everyone else stays on "Regular Member" permissions. Within the same service, you can give each member different permissions.

1. In the Users list, click the ∨ (expand) on the row of the member you want to give different permissions.
2. Open the Role dropdown in the Permissions section.
3. Choose "Premium Member" from the list.
4. Click Save.

To take back the permissions you assigned separately and put the member back in line with everyone else, choose Follow Default (currently Regular Member) in that member's Role dropdown and click Save. How to create and edit the permission bundle you grant members (ServiceUserRole) itself is covered in Member Roles and Permissions.

Letting a member clean up other people's posts

Sometimes you want one member to help clean up the inappropriate things other members have left behind. Something like picking out and deleting advertising reviews on the review board. For that, you can give one member the permission to clean up what other members wrote too.

A member who receives this permission can also delete what other members wrote. But this is a narrow permission that is added for deletion only. They cannot edit what others wrote, nor see anything they could not see before. It does not grant operator (team) permissions either.

There is one more thing to know. This permission sits on top of the range the member's Role already allows. So if the member's Role does not allow deleting reviews in the first place, granting this permission still will not let them delete reviews. For the member to be able to delete, that member's Role must already allow deletion of the target in question.

1. In the Users list, click the ∨ (expand) on the row of the member you want to give this permission.
2. In the Permissions section, turn on Admin.
3. Click Save.

Once you turn on Admin and save, an Admin badge appears next to that member's name in the list.

Sharing out this cleanup permission lets you leave it to your shoppers to clean up inappropriate posts themselves. Operators do not have to delete everything by hand. Still, because the permission is broad, it is best to grant it only to members you trust.

What to do next

• Service Member Login: Covers how to turn on member login for the first time, connect social login, and decide whether new sign-ups need approval and what the Default Role is.
• Member Roles and Permissions: Covers how to create the permission bundle you grant members (ServiceUserRole) and how to let members handle only what they wrote.
• Inviting Members and Granting Permissions: Covers how to invite and grant permissions to the operators (the team) you work with, rather than to signed-up members.
• API Reference: Covers technical specifications such as request formats for working directly, from a program, with the content that signed-up members read and write.