CiviCRM Community Forums (archive)

Load will probably not be an issue for you. Depending on what those 50 concurrent users are doing  (i.e. if you experience any slowness) you may need to tune the underlying webserver (apache) or, more likely, the database (mysql) server. Other Civi installs exceed your numbers, but you would be among the larger installs.

You might try the case studies, for a reference (http://wiki.civicrm.org/confluence/display/CRMDOC/Case+Studies), but one is not jumping out at me off the top of my head. CivicActions and Trellon and others (http://civicrm.org/professional) have been consultants on this scale of project.

Within the ACL system, you could create a group of a single record and restrict access that way, but there is no direct per contact structure. You'll need to think a lot about how ACLs will impact your load.

Hi,

The ACL system is already quite detailled and allows to grant/deny access to individual features. They are financial informations linked in several places (eg. registration fees, donation, memberships...). Based on what you need, it might already be there, or shouldn't be too complicated to create and add rules.

I'd suggest not to focus on these details too early on your evaluation, and rather get a sense if you think your users will like the interface and if the way it's organised will fit your needs. More importantly, if the way the system has evolved over the past versions make you comfortable in its future  as something that will grow with you.

As for the fine tuning and tiny details, plan a budget for that, you will find providers, either Civi directly or one of the IT companies using it. This is an open source product, it is in general easier and cheaper to customize if it needs change at the code level (most is likely only to be templates and configurations).

Please share with us the result of your analysis, especially if you decide to go for another solution, I'd love to know what you consider missing for a big install.

X+