Skip to main content

Teen accounts under parent accounts? Restricting DMs for teens?

Hi everyone! I want a space for teens (13-19) and a separate space for parents to discuss the college application process.

What kind of measures could I put in place to protect the teens?

Can I disable 1:1 messaging only for certain users?

Can there be subaccounts to where the parents have an account, and the teen’s account is under their parent’s?

Ross Rabette

I have a similar use case re sub accounts - there is nothing in Fluent. I reached out to https://aamportal.com/

they might have a solution

Ross Rabette

'AM does not have a built-in feature to directly linkΒ parentΒ andΒ childΒ WordPressΒ accounts. However, it is possible to establish such relationships by utilizing theΒ _usermetaΒ table inΒ WordPress. This approach allows you to store custom metadata that defines the relationship betweenΒ parentΒ andΒ childΒ accounts.

If you are using Fluent Forms to create accounts, you can still implement this functionality. After anΒ accountΒ is created via Fluent Forms, you can programmatically add metadata to theΒ _usermetaΒ table to establish theΒ parent-childΒ relationship. For example, you could store theΒ parentΒ account's user ID as metadata for theΒ childΒ account.

Once the relationship is established, you can leverage AAM's User Governance service to manage permissions and define what actions theΒ parentΒ andΒ childΒ accounts can perform. For instance, you can configure AAM to allow theΒ parentΒ accountΒ to view or manage specificΒ childΒ accounts while restricting access to others.

Here’s an example of how you might implement this:

  1. Create the Relationship: When aΒ childΒ accountΒ is created, add a custom field in the `_usermeta` table, such as `parent_user_id`, and store theΒ parentΒ account's user ID.
  2. Leverage AAM: UseΒ AAM's PHP frameworkΒ to define what theΒ parentΒ accountΒ can see or manage. For example, you can use theΒ `Users`Β service in AAM to retrieve allΒ childΒ accounts associated with aΒ parentΒ accountΒ and define specific permissions for them.

This approach requires some custom development, but it provides a flexible way to link accounts and manage their relationships effectively.

I can help with developing any custom functionality, however, it is outside of a regular customer suppor'

Kaneisha G.

Ross RabetteΒ thank you for your thorough response! I will likely reach out for more details about custom development once I’m a bit further along.

I think I saw elsewhere you were looking into BetterMessages to replace FluentMessaging? If so, you could use it's built-in messaging restriction feature to do exactly this. For the separate spaces, you could use FluentCRM tags to auto-assign certain users to certain spaces. There wouldn't be any "official" link between accounts and sub-accounts, but you'd have very similar functionality.

Kaneisha G.

Stuart McKelvieΒ that could work well for me!