I am creating a Gemini site to implement CCB's

The basic "idiom" is this:

Projects == Change Control Boards (CCBs);
Resources == CCB members (voting members);
Custom data includes a view into project resources so that who should "vote" on a submittal (and their vote) can be recorded (see other post for issue with recording custom data changes in history);
Default project  Security Scheme is "Issue Creator" so that anyone can create (submit a change request), and comment when requested.
ONLY CCB members ("Resources") should have issue worker Security Permissions (since they record their vote, among other things, by editing the issue).

-----
What I would like to do:

I would like to be able (in this installation) to modify / augment gemini_updateprojectresource() so that, in addition to adding or removing a resource, this SPROC also automatically "promotes" user settings/roles so that the resource (in effect) gets some list of additional project permissions that will result in effect giving them "Issue Worker" status.   It would seem the way to do this is to create a lookup table that looks up the permissions to be added for "resources" (removing would be harder, but could be done by recording changes in another table, then "rolling back").

Anyway, in looking at the tables and sprocs, I don't immediately see how to do this.   It would appear that I need to add (?) an entry in the userroles table to accomplish this.

Does that sound about right?  Anything else I need to think about?

Thanks,
Yarko