Skip to Content
avatar image
Former Member

Limit iView functionality based on user

I've got a few iViews where I need to limit the options or features based on the user/role/group. The intention is to have a single iview that allows all users to view data and admin type users to edit.

What is the consensus on the best way to do this? It seems I should be able to do this with security zones and/or acl, but I can't find any examples. Alternatively, I could add a component profile attribute of the admin role and check for it manually.

Any suggestions?


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Aug 11, 2004 at 07:10 AM


    avoid defining a security zone, as these are used only for making the component executable directly (without an iView).

    How about this:

    - define a profile property named 'editable'

    - create an iView in the admin role, having the property to 'true'

    - create an iView in the user role, having the property set to 'false'



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks for the response. I was afraid this was the case when I was unable to find any examples of this.

      My solution is similar to what you propose. I've got a component property- "AdminRole" that can be defined via Content Administration. Then, in the iview, I check the roles to which the current user is assigned and enable the editor functions if the user is a member of the entered role.