doesn't work.. i've granted the user full admin rights in ALL the development directories. still no joy..
It's still strange that the Windows Administrator account is able to read/write in the workspace path and a regular user (with the permissions granted as you said) not.
Can you try to create the workspace in a different location? Maybe the Desktop, just to test if your regular windows user is able to use that path.
At the end of the day the Plastic client is just a process that's started with a certain user, the IO operations made by the Plastic SCM client are done by the user that started the process so if the Administrator user can work it must be something related with the Windows security.
AND if user creates new workspace using right mouse admin to open SCM i can't see the new workspace?
Each windows/linux user has their own workspaces list, so, if you create one workspace with the admin user it's stored for the admin session. You will find the workspaces list inside a file called "plastic.workspaces", this file is located in the Local user directory (C:\Users\XXXXX\AppData\Local\plastic4). If you copy this file and you place it into the cm.exe location path ("C:\Program Files\PlasticSCM4\client" by default) all the system users will share the workspaces list.