Question regarding multiple users/permissions levels

Next topic

Author	Message
Taylor Ogden	Friday 02 July 2010 11:13:22 am Hey everyone, I work at a treatment center for teenagers and we are required by the state to document every little thing that we do with the clients. We currently have an online system set up, but I hate it. I've been looking around at other alternatives and I've come across eZ Publish. I'm impressed with what I see. However, before I dive in and start working on things I want to get some input from people who have used the software. Here's what I'm looking to set up: - A page for every client, where all information on them is stored. This includes addresses, age, medical info, recent documentation made on the client, etc. - Multiple users with different levels of permissions. These would be along the lines of "staff" who would be able to edit basic information on a client page (such as adding documentation). "Parents" who would be presented with a page displaying basic info regarding their child, but no option to edit anything. And "Supervisor" which would allow the creation of new client pages. - The entire system would need to be password protected. I'm basically just wondering if eZ Publish would be a good choice to set up a system like the one I've described. What are your thoughts/opinions? Thanks!
Ivo Lukac	Saturday 03 July 2010 3:01:41 am Hello Taylor and welcome to #ezcommunity :) Regarding the ez access control subsystem, you can do far more with it. Take a look at these links: http://ez.no/doc/ez_publish/user_manual/4_x/daily_tasks/managing_users http://ez.no/doc/ez_publish/user_manual/4_x/the_administration_interface/the_user_accounts_tab/roles_and_policies http://ez.no/doc/ez_publish/user_manual/4_x/the_administration_interface/the_user_accounts_tab Cheers http://www.linkedin.com/in/ivolukac http://www.netgen.hr/eng/blog http://twitter.com/ilukac
Doug Brethower	Saturday 03 July 2010 5:10:13 am Welcome Taylor. As Ivo says, you would be scratching the surface of the permissions capabilities. Client page you describe is likely a custom content CLASS to define and restrict inputs to exactly information desired, no more, no less. To restrict access, one content SECTION per client may be the easiest way to restrict parents to just their child's info. If you have hundreds of teens, you may want to do some load testing. eZ Publish makes it easy enough to do just about any form of data management you desire. Understanding nomenclature and getting started without getting lost are the two greatest difficulties. In this case, start with CLASS and SECTION and hopefully your study of the possibilities will unfold quickly. Custom CLASS howto step by step: http://webportalmaster.com/index.php/eng/eZ/HowTo/Create-a-Kindergarten-class-in-eZ-Publish Sections and permissions are very powerful, somewhat difficult to grasp first few times through. Particularly when actually working with them in the GUI it can get confusing. Hopefully this link lends some understanding and serves as a starting point for exploring SECTIONS: http://webportalmaster.com/index.php/eng/eZ/HowTo/Create-Policies-and-Restrict-Access-in-eZ-Publish Doug Brethower Apple Certified Technical Consultant, Southwest, MO USA http://share.ez.no/directory/companies/lakedata.net

Author

Message

Friday 02 July 2010 11:13:22 am

Hey everyone, I work at a treatment center for teenagers and we are required by the state to document every little thing that we do with the clients. We currently have an online system set up, but I hate it. I've been looking around at other alternatives and I've come across eZ Publish. I'm impressed with what I see. However, before I dive in and start working on things I want to get some input from people who have used the software.

Here's what I'm looking to set up:

- A page for every client, where all information on them is stored. This includes addresses, age, medical info, recent documentation made on the client, etc.

- Multiple users with different levels of permissions. These would be along the lines of "staff" who would be able to edit basic information on a client page (such as adding documentation). "Parents" who would be presented with a page displaying basic info regarding their child, but no option to edit anything. And "Supervisor" which would allow the creation of new client pages.

- The entire system would need to be password protected.

I'm basically just wondering if eZ Publish would be a good choice to set up a system like the one I've described. What are your thoughts/opinions?

Thanks!

Ivo Lukac

Saturday 03 July 2010 3:01:41 am

Hello Taylor and welcome to #ezcommunity :)

Regarding the ez access control subsystem, you can do far more with it. Take a look at these links:

http://ez.no/doc/ez_publish/user_manual/4_x/daily_tasks/managing_users

http://ez.no/doc/ez_publish/user_manual/4_x/the_administration_interface/the_user_accounts_tab/roles_and_policies

http://ez.no/doc/ez_publish/user_manual/4_x/the_administration_interface/the_user_accounts_tab

Cheers

http://www.linkedin.com/in/ivolukac
http://www.netgen.hr/eng/blog
http://twitter.com/ilukac

Doug Brethower

Saturday 03 July 2010 5:10:13 am

Welcome Taylor.

As Ivo says, you would be scratching the surface of the permissions capabilities.

Client page you describe is likely a custom content CLASS to define and restrict inputs to exactly information desired, no more, no less.

To restrict access, one content SECTION per client may be the easiest way to restrict parents to just their child's info. If you have hundreds of teens, you may want to do some load testing.

eZ Publish makes it easy enough to do just about any form of data management you desire. Understanding nomenclature and getting started without getting lost are the two greatest difficulties. In this case, start with CLASS and SECTION and hopefully your study of the possibilities will unfold quickly.

Custom CLASS howto step by step:

http://webportalmaster.com/index.php/eng/eZ/HowTo/Create-a-Kindergarten-class-in-eZ-Publish

Sections and permissions are very powerful, somewhat difficult to grasp first few times through. Particularly when actually working with them in the GUI it can get confusing. Hopefully this link lends some understanding and serves as a starting point for exploring SECTIONS:

http://webportalmaster.com/index.php/eng/eZ/HowTo/Create-Policies-and-Restrict-Access-in-eZ-Publish

Doug Brethower
Apple Certified Technical Consultant, Southwest, MO USA
http://share.ez.no/directory/companies/lakedata.net

eZ debug

Timing:	Jan 30 2025 16:08:55
Script start
Timing:	Jan 30 2025 16:08:55
Module start 'layout'
Timing:	Jan 30 2025 16:08:55
Module start 'content'
Timing:	Jan 30 2025 16:08:55
Module end 'content'
Timing:	Jan 30 2025 16:08:55
Script end

Main resources:

Total runtime	0.0235 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0048	588.2578	151.2266
Module start 'layout'	0.0048	0.0034	739.4844	220.7344
Module start 'content'	0.0083	0.0136	960.2188	1,001.8047
Module end 'content'	0.0219	0.0016	1,962.0234	33.9922
Script end	0.0234		1,996.0156

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	11.2415	14	0.0002
Check MTime	0.0011	4.5328	14	0.0001
Mysql Total
Database connection	0.0008	3.5092	1	0.0008
Mysqli_queries	0.0020	8.3679	3	0.0007
Looping result	0.0000	0.0426	1	0.0000
Template Total	0.0011	4.9	1	0.0011
Template load	0.0009	3.8413	1	0.0009
Template processing	0.0002	1.0002	1	0.0002
Override
Cache load	0.0006	2.6959	1	0.0006
General
dbfile	0.0024	10.3206	8	0.0003
String conversion	0.0000	0.0244	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0002 secs