This archived community thread from the APG vNext support forum discusses: Information on Private User & Custom Group Permissions for Forum Management.
About This Topic
In the forum management interface for a forum, you will see two buttons: manage private users and manage custom group permissions.[attachment=privatecustomgr...
Getting Help with APG vNext
APG vNext is a powerful ASP.NET forum and community platform. For questions related to this topic:
- Browse the Knowledge Base for documented solutions
- Search the community forum for similar threads
- Check the FAQ for common questions and answers
- Review the Installation and Upgrade guides
If you need direct assistance, the support team is active in the community forum.
Understanding Permissions in APG vNext
APG vNext uses a layered permission system that lets administrators control exactly what each user group can do in each forum section. Permissions cascade from global defaults down to per-forum overrides, giving you precise control without having to configure every forum from scratch.
User Groups vs. Custom Groups
APG vNext distinguishes between built-in user groups (Administrators, Moderators, Registered Users, Guests) and custom groups that you create yourself. Built-in groups have fixed roles in the system, while custom groups give you flexibility to create tiers like Premium Members, Staff, Beta Testers, or regional sub-communities with different access rights.
To create a custom group, go to Admin > User Groups > Add Group. Give the group a name, set its display priority (which determines badge order when a user belongs to multiple groups), and configure the base permission set it inherits from. Custom groups can inherit from any existing group, letting you build permission hierarchies without repeating configurations.
Private Forums and Group-Based Access
To create a private forum visible only to specific groups:
- Navigate to Admin > Forums > Edit Forum for the target forum.
- Under Permissions, set the default permission to deny all access for Guests and Registered Users.
- Add specific group overrides that grant read and post access to the groups you want to allow.
- Save changes. The forum will now be invisible to users not in the allowed groups.
APG vNext also supports a hybrid approach where the forum is visible (listed in the forum index) but posting requires group membership. This is useful for announcement sections where staff post and members can read but not reply.
Per-Forum Permission Overrides
Every permission in APG vNext can be set at three levels: global default, group default, and per-forum override. The per-forum override always wins. This means you can have a group that can post everywhere by default, but deny them posting rights in a specific sensitive forum, or vice versa.
Common permission types you can configure per forum include: View Forum, Read Posts, Create Topics, Reply to Topics, Edit Own Posts, Delete Own Posts, Upload Attachments, Use Polls, and Moderate Posts. Each can be set to Allow, Deny, or Inherit (which falls back to the group default).
Private User Permissions
In addition to group-based permissions, APG vNext supports per-user permission overrides for edge cases. This lets you give a specific user elevated or restricted rights without changing their group membership. Navigate to Admin > Users > Edit User > Permissions to set individual overrides. These are useful for situations like temporarily restricting a misbehaving user from a specific forum, or granting a trusted community member moderator-level access to one section without making them a full moderator.
Moderator Assignments
Custom groups can be assigned as moderators for specific forums. A moderator assignment gives the group members the ability to edit and delete any posts, move topics, lock and unlock threads, and approve queued posts in their assigned forums. Unlike global administrator permissions, forum-level moderator rights are scoped only to the assigned forums, making it safe to promote trusted community members to moderator roles without giving them site-wide admin access.
Best Practices for Forum Permission Management
Keep permission configurations as simple as possible. Start with sensible group defaults and use per-forum overrides sparingly. Document your permission structure in a simple table so that future administrators can understand why specific configurations were made. Periodically audit permissions by logging in as a test user in each major group to verify access is as expected. APG vNext's permission inheritance model is powerful but can produce unexpected results when multiple group memberships combine, so testing is essential after any significant permission change.
When creating restricted forums, always test access from an incognito window using a test account in the relevant group before announcing the forum to members. This prevents the embarrassment of a private forum that turns out to be publicly accessible due to a permission misconfiguration.
Troubleshooting Permission Issues
If a user reports they cannot see or access a forum they should have access to, first verify their group membership is correctly assigned under Admin > Users > Edit User > Groups. Next, check the forum's permission overrides to confirm the group has an Allow entry. Finally, clear the APG vNext application cache, as permission changes sometimes require a cache flush to take effect immediately. If the issue persists, use the built-in permission tester (if available in your version) or create a dedicated test account in the problem group for direct verification.
Looking for more help? Browse the support forum or check the Knowledge Base.