Mark"
To: arslist@ARSLIST.ORG
Sent: Thursday, February 26, 2009 9:30:26 PM
Subject: Re: Data level Security
**
I have something similar. First I assigned the Assignee Group as the only
permission in the Request ID field. The I created a field with a ID of 112.
Using your example, workflow
rsday, February 26, 2009 8:30 PM
To: arslist@ARSLIST.ORG
Subject: Re: Data level Security
**
I have something similar. First I assigned the Assignee Group as the only
permission in the Request ID field. The I created a field with a ID of 112.
Using your example, workflow on create places YYY in th
SList)
[mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor
Sent: Thursday, February 26, 2009 6:48 PM
To: arslist@ARSLIST.ORG
Subject: Re: Data level Security
You could potentially use multitenancy to accomplish this. You would
essentially create another company with a support group that corresponds
to
That's a pretty horrid way of doing it. If the data is sensitive, you
aren't protecting it with this approach. Read up on row level access, which
is controlled by setting the permissions on field id 1.
Bear in mind that active links are processed on the client side. You can
trust them to work a
You need to read about row level permission. Using Assigned Group (112) you
can make is so that only users who have the group value that is in that
field can see the record.
On Thu, Feb 26, 2009 at 6:12 PM, Sugavanam K K wrote:
> ** Following is the Requirement which I received form my client, I
You could potentially use multitenancy to accomplish this. You would
essentially create another company with a support group that corresponds to
group YYY and add the users to that group. You would then add the new company
to their list of Access Restrictions on the People form and make sure
6 matches
Mail list logo
