D
Dale Fye
I'm working on upgrading an application that is currently used by a handful
of individuals with unlimited access to the db. The organization has decided
to expand use of the application to a whole realm of people within the
organization. Each of whom will have limited access to forms, and even
fields within forms.
I'm thinking about a UserRoles table that would include:
UserID Role RoleVal
Dale Opns Yes
Steve Div Budget Div2
Tom Div Opns Div1
Dale Admin Yes
In some instances, just assigning someone to a group (admin, operations,
budget) will be sufficient. However, there are fields in the database where
the divisions within the company will only be able to recommend changes to a
field value, rather than actually change the values. These recommended
changes would then be routed through a workflow to individuals with
permissions to accept or reject the changes, up to a final approval authority.
Anybody have any recommendations about how to structure this table, and/or
the input forms?
of individuals with unlimited access to the db. The organization has decided
to expand use of the application to a whole realm of people within the
organization. Each of whom will have limited access to forms, and even
fields within forms.
I'm thinking about a UserRoles table that would include:
UserID Role RoleVal
Dale Opns Yes
Steve Div Budget Div2
Tom Div Opns Div1
Dale Admin Yes
In some instances, just assigning someone to a group (admin, operations,
budget) will be sufficient. However, there are fields in the database where
the divisions within the company will only be able to recommend changes to a
field value, rather than actually change the values. These recommended
changes would then be routed through a workflow to individuals with
permissions to accept or reject the changes, up to a final approval authority.
Anybody have any recommendations about how to structure this table, and/or
the input forms?