Level 1
Are you planning on billing both employees and agencies (teams) or simply agencies (teams) and don't want to bill per user?
Mar 22, 2018
2
Level 2
User and Team Billing (Separate Registration)
Hi there,
Here's my use case. I'm looking at using Team's. An Agency will be a team, and there can be a number of agencies. An agency can have a number of users in, but I want to bill per agency (per team). I'm not bothered how many users are in an agency. Let's say for example, I want to charge $10 per month per agency.
What I want to do then is to allow potential employees to register on the site as individual users. They don't belong to a team or agency, but I want to bill them $2 per month. The key thing is that they don't belong to a team.
I know I can bill them separately, I just don't understand how I can register people into a team, and then register people so they don't join a team. When I add the canJoinTeams() into the User, it forces them to join a team, or create a team on registering.
I know one solution would be to create a team called Employees and then add all employees into this team but bill them individually, but I'd rather not use the Team's functionality for those.
Has anyone implemented something similar?
Kind regards Paul Pounder
Level 2
Ideally I’d like to bill both users (employees) and agencies (teams).
I’ve sctually overridden the hasTeam middleware and brought in a roles plugin. That way I can give team members a specific role and check for that in the hasTeam method.
Seems to be working ok so far.
Regards Paul
Please or to participate in this conversation.