We don't want anybody to do it for us - just a ideas on what the best
approach would be.
The Aros are:
Reviewers
Approvers
Administrators
Seniors
The ACO on the other hand is where things get tricky, so we're just
trying to get ideas, not code. Because in theory we have 2 separate
ones.
The
On Aug 29, 1:16 pm, Colombian [EMAIL PROTECTED] wrote:
We don't want anybody to do it for us - just a ideas on what the best
approach would be.
The Aros are:
Reviewers
Approvers
Administrators
Seniors
The ACO on the other hand is where things get tricky, so we're just
trying to get
Thanks Mark,
The permissions are based on 2 things.
1. The status (state) of the project.
2. The user roles. (user can have multiple roles, but most of the
permissions would be set this way)
If it was one or the other, we would be ok using the built in ACL, but
since we are running permissions
I was hoping to get good pointers as to the best way to tackle our
problem:
We have 4 roles. (4 'aros')
However, the permissions depend on the project status.
While the status is 'draft' some aros can edit/delete etc.
But when the project status is submitted or finalize, the permissions
would
Paste your code and your approach, a test approach at least. I don't
think someone will actually *do* it for you. But many people can point
out what you're missing
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
