Details

    • Type: Feature Request Feature Request
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 6.0.12 EE, 6.1.0 CE RC1
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Tomcat 7.0.10 + MySQL 5.1.56. Firefox 3.6.16. 6.0.x Revision 77500.
      Tomcat 7.0.12 + MySQL 5.1.56. Firefox 3.6.16. 6.1.x Revision 77640.
    • Branch Version/s:
      6.0.x
    • Similar Issues:
      Show 5 results 

      Description

      To reproduce:

      • login as admin
      • create a custom field for organizations
      • create an organization and fill in its custom filed value
      • create a user
      • assign the user as a member of the created organization
      • assign the user organization owner role
      • login as the new user
      • go to control panel and go to organizations
      • select the owned organization to edit
      • go to custom fields tab
      • there are no fields displayed

        Activity

        Hide
        Jang Kim (Inactive) added a comment -

        Andrius,
        This issue is not a bug and it is working as designed.
        Here's explanation why this is not a bug:

        Custom fields are currently only scoped to the company. This means that it could very well be a portal admin that set a custom field on the organization that they do NOT want the org admin to modify.
        Thus if you want Org admins to be able to update or other manipulate the custom field you should create a "regular" role with the permissions you need, and assign that Org admins this role.

        Let me know if you have any questions.
        Thanks,

        Jang

        Show
        Jang Kim (Inactive) added a comment - Andrius, This issue is not a bug and it is working as designed. Here's explanation why this is not a bug: Custom fields are currently only scoped to the company. This means that it could very well be a portal admin that set a custom field on the organization that they do NOT want the org admin to modify. Thus if you want Org admins to be able to update or other manipulate the custom field you should create a "regular" role with the permissions you need, and assign that Org admins this role. Let me know if you have any questions. Thanks, Jang
        Hide
        Andrius Kurtinaitis added a comment -

        I just logged in and checked if I can assign needed permissions.

        It is not possible to assign permissions on custom fields to Organization scoped roles.
        The custom field permissions form contains only regular roles - no organization scoped roles.

        Even if it is working as designed, it is then design issue. It is not good that organization admin cannot be restricted to edit his (and only his) organization fields.

        Show
        Andrius Kurtinaitis added a comment - I just logged in and checked if I can assign needed permissions. It is not possible to assign permissions on custom fields to Organization scoped roles. The custom field permissions form contains only regular roles - no organization scoped roles. Even if it is working as designed, it is then design issue. It is not good that organization admin cannot be restricted to edit his (and only his) organization fields.
        Hide
        Jang Kim (Inactive) added a comment -

        Andrius,
        There are incidents that a portal admin would add organization custom fields that a portal admin do not want the org admin to modify. So the behavior that you desire will not be implemented.

        So you can not assign permissions on custom fields to Organization scoped roles. However, you can achieve the behavior you want by setting Power User role(or any regular role) to have update/view permission for custom field and assign to organizational admin.

        Show
        Jang Kim (Inactive) added a comment - Andrius, There are incidents that a portal admin would add organization custom fields that a portal admin do not want the org admin to modify. So the behavior that you desire will not be implemented. So you can not assign permissions on custom fields to Organization scoped roles. However, you can achieve the behavior you want by setting Power User role(or any regular role) to have update/view permission for custom field and assign to organizational admin.
        Hide
        Andrius Kurtinaitis added a comment -

        I know I can use some existing global role or I can create a new one.
        The problem is that it is not possible to allow the admins of the organizations to manage his own organization.
        If I assign the permission to a global role, then all users belonging to this role have right to edit this field. All admins of all other organizations. Which is not right.
        The alternative would be to create a role for every org. Which is even worse.

        There is no way to allow org scoped resource to have assigned permission to a org scoped role. This seems to me like a serious design issue. I do not understand why you do not want to fix it.

        Show
        Andrius Kurtinaitis added a comment - I know I can use some existing global role or I can create a new one. The problem is that it is not possible to allow the admins of the organizations to manage his own organization. If I assign the permission to a global role, then all users belonging to this role have right to edit this field. All admins of all other organizations. Which is not right. The alternative would be to create a role for every org. Which is even worse. There is no way to allow org scoped resource to have assigned permission to a org scoped role. This seems to me like a serious design issue. I do not understand why you do not want to fix it.
        Hide
        Raymond Auge added a comment -

        It's not that we don't want to fix it.

        What would have to happen is that custom fields would have to support being scoped to a group. Once scoped to a group then the org admin could have control over it.

        Since custom fields are currently only scoped globally and there is no acceptable change that should allow a scope role (org or site) to take control of a globally scope resource, unless that change is to support scoping of custom fields.

        Show
        Raymond Auge added a comment - It's not that we don't want to fix it. What would have to happen is that custom fields would have to support being scoped to a group. Once scoped to a group then the org admin could have control over it. Since custom fields are currently only scoped globally and there is no acceptable change that should allow a scope role (org or site) to take control of a globally scope resource, unless that change is to support scoping of custom fields.
        Hide
        Andrius Kurtinaitis added a comment -

        I do not know the internals of Liferay good enough, but I think if a custom field belongs to an organization, then it is already in some sense group scoped.
        Is'nt it?

        Show
        Andrius Kurtinaitis added a comment - I do not know the internals of Liferay good enough, but I think if a custom field belongs to an organization, then it is already in some sense group scoped. Is'nt it?
        Hide
        Raymond Auge added a comment -

        The custom field is a field which belongs to the Organization "entity", not necessarily to the Organization "instance".

        Show
        Raymond Auge added a comment - The custom field is a field which belongs to the Organization "entity", not necessarily to the Organization "instance".
        Hide
        Andrius Kurtinaitis added a comment -

        You always edit field value of an "instance", not some abstract "entity".

        Show
        Andrius Kurtinaitis added a comment - You always edit field value of an "instance", not some abstract "entity".
        Hide
        Randy Zhu added a comment -

        In preparation for Ideation; we are merging New Feature and Improvement tickets into a singular ticket type called “Feature Request”. Additional information to follow soon.

        Show
        Randy Zhu added a comment - In preparation for Ideation; we are merging New Feature and Improvement tickets into a singular ticket type called “Feature Request”. Additional information to follow soon.

          People

          • Assignee:
            SE Support
            Reporter:
            Andrius Kurtinaitis
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development

                Structure Helper Panel