Suppose a SaaS product charges per project, whereby the first project you own is free. Ideally, users would open up a project and invite a few members to work on it. If more projects are needed, the same user within a team would open up another project which then is charged for.
With above restrictions, nothing would stop a team from rotating project ownership to make use of the free project per user, effectively gaining
n free projects for a team size of
What criteria could you use to detect such a scenario and how could you fix it?
Things I've thought of
- You can only be member of at most one "free" project. That's hard to enforce because you can't really label any project "free" or "paid" if you charge for
n-1projects. Which one is the "free" one?
- Reserve certain permissions for the project owner only. That's not feasible either because in the context of large organisations, there should probably be multiple members with full access.