Latest Contributions by DValley

Thank you for your response Marcelo.  I'm not sure I described our issue very well (it's been a long week!), so here is some additional info and an example. We have roles already setup on our versioned gdb.  These roles control the permissions given to each user (as you described above).  We have several child versions of the parent gdb that all users can at least see, but may not be able to edit, for example, depending on the permissions applied to their role. EXAMPLE: DB Connection1 - shows all available feature classes (Trees, Rocks, Lakes) - all users can see/read, but only users with DB1 role can edit, etc. DB Connection2 - shows only Sand, Grassland, Wetlands- all users can see/read only users with DB2 role can edit, etc. I can see several feature classes in the data owner view of the SDE that are not displayed in either of the above connections (Streams, Clouds).  I would like to make these at least visible and readable in both connections.  To return to my example, once I make these two FCs visible/editable, users will see the following: DB Connection1 - Trees, Rocks, Lakes, Clouds, Streams. DB Connection2 - Sand, Wetlands, Clouds, Streams. Can I do this from the data owner account and how?  -OR- is this an admin/gdb admin function?  I suspect that I may need to add the 'new' FCs to the applicable roles to make them visible/usable? ... View more