Hide specific data schema

[#1]

Hi everyone,

I was wondering if it is possible to hide a specific data schema except for a certain user?

Why do I need this? Our developers need to have the right 'admin' so that they have access to all areas in Campaign and can adjust these. But they shouldn't be able to edit or delete users in access management - they should be still visible though.

Therefore I adjusted the data schema operators:

<!-- No other user can add users than the one mentioned below. -->

    <sysFilter name="writeAccess">

        <condition enabledIf="$(loginId)!=32387063" expr="FALSE"/>

    </sysFilter>

This works fine. But if a developer wants to, he can delete these rows since he has the right to edit schemas - which he needs to keep! So, if I hide it from everyone except the Administrator it should be fine.

Thanks in advance!

Bella

[#2 · Accepted solution]

Hi Bella,

I didn't see it was about the operator schema. The user will also need a write access to this table as there are updates for audit (last time operator modified, created an object, last connection, etc..)

I will add both read and write access to the operator

<sysFilter name="readAccess">

<condition enabledIf="hasNamedRight('myRight')=false" expr="FALSE"/>

</sysFilter>

<sysFilter name="writeAccess"> 

<condition enabledIf="hasNamedRight('myRight')=false" expr="FALSE"/> 

</sysFilter>

I did couple of tests and the admin right overwrite all rights in ACC

with admin right

without admin right but with new name right deleteOperator

Thanks

David

[#3]

Hi Bella,

You can try to create a named right

<sysFilter name="readAccess"> 

<condition enabledIf="hasNamedRight('myRight')=false" expr="FALSE"/> 

</sysFilter>

Only operator that have this right will be able to read the schema. Also keep in mind that admin right can overwrite all the rights so you may need to do some tests.

Thanks

David

[#4]

Hi David,

I tried this before declaring a specific user who should be able to see this schema.

Result: no one was able to login on client console anymore. No one had the right even the user who should have had it according to the code. In the end we had to use the internal administrator to delete the rows in schema operators. Afterwards everyone had access again...

Do you have another idea?

Thx,

Bella