Soft and hard limits for concurrent users per tenant.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No file or test is identified. Start by locating the tenant-override handling and the meeting creation and join-link entry points; done means soft and hard concurrent-participant limits can be configured per tenant and enforce the stated creation, joining, and error-page behavior.
Written by the indexing model from the issue text.
Description
Limiting the participants per meeting is already possible with tenant overrides, but some scenarios can benefit from the ability to also limit the total number of users across all meetings.
Proposal: Allow to configure soft and hard limits for concurrent participants per tenant.
- When the soft limit is reached, no new meetings can be created. Users will still be able to join existing meetings.
- When the hard limit is reached, then no meetings can be created or joined. The join link will instead return an error page explaining the issue.
- Dominant language
- Python
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from defnull/bbblb
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·