Roles Based Document Management - Any Tutorials?
-
Hi there guys n girls, I am currently developing a document management system. There are a flexible number of roles and each document can have its access rules set so it can only be accesssed by users belonging to certain roles. Each user can belong a a number of roles too. So in essense there is a many to many relationship between roles and users and a many to many relationship to documents and roles. I'm using the built in .NET membeship / role features and was wondering if anyone had come across a tutorial which might cover this kind of thing. Really want a good point of reference to implement best practise and not found anything on the web yet which covers exactly what i'm after. Thanks in advance Steve
"Gödel proved that any formal system that defines the primitive recursive functions must be either incomplete or inconsistent. In particular one could not prove from within the system that the system itself was consistent even though the question could be formulated within the system."
-
Hi there guys n girls, I am currently developing a document management system. There are a flexible number of roles and each document can have its access rules set so it can only be accesssed by users belonging to certain roles. Each user can belong a a number of roles too. So in essense there is a many to many relationship between roles and users and a many to many relationship to documents and roles. I'm using the built in .NET membeship / role features and was wondering if anyone had come across a tutorial which might cover this kind of thing. Really want a good point of reference to implement best practise and not found anything on the web yet which covers exactly what i'm after. Thanks in advance Steve
"Gödel proved that any formal system that defines the primitive recursive functions must be either incomplete or inconsistent. In particular one could not prove from within the system that the system itself was consistent even though the question could be formulated within the system."
I have done a similar application, but without using membership providers. I created custom classes to manage roles. What I did is keeping the roles and users belongs to that in a database which my custom classes can read and validate the role.
All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia My Website | Ask smart questions