Yeah, its good one this! "Participants" are not controlled like any of the other security / access rights in Clarity, a completely different security model applies! The answer actually is in the text you posted, but you don't realise it! There is this "special" role associated with a project, known as the "Collaboration Manager". When a project is CREATED, then the user who created the project becomes it's "Collaboration Manager". The "Collaboration Manager" controls the "particpiant access" to the project and they can add resources as "participants" (as opposed to "Staff") on the project. They can also make other existing participants into "Collaboration Managers". The only person who can REMOVE participants from the project is a (any) "Collaboration Manager". If you look on the "Participants" tab you can see who the current "Collaboration Manager" is - they will have a funny icon next to their name. If you have never changed this, then the ONLY "Collaboration Manager" will be the original project creator and ONLY they can remove the particpants. (Not even system admins can do this otherwise!). The workaround to adding participants if you are not a "Collaboration Manager" is to add them as a TEAM member and then remove them, this leaves Participant access - this feature is what you have stmbled upon!! I said it was great didn't I? ;-) So you have to log on as the project creator user and remove the participants OR set up an admin user as another "Collaboration Manager" for the project so you don't have to this again! David MortonCapgemini