I'm currently working on a project which requires me to make specific nodes for specific users private without the use of Roles.
I've checked a few access modules and all require the use of roles to make it work.
Lets say i have a new content type.
I crate a node from it.
I should see a "private" or "public" check box available.
If i check "private" and save the node, i should see a "Permission/Grant" tab on the view page.
Inside "Permissions/Grant" i'll need the ability to add specific users who have rights to see this node.
This is what I've seen in the Organic Groups module and would like to know if there's another module out there that only ships with that functionality.
If not, what would be the best way to make this work?
Thank You,
Emir.

Comments
I'm guessing that the reason
I'm guessing that the reason roles won't work for you is that you're going to have a lot of unique sets of users that need access to unique modules, correct? If not, let me know why roles are bad here--it could be significant.
I think the Node Access User Reference module for D6 and D7 might be a possible solution. I haven't tried it myself, but it looks like it will allow you to hook a node's access privileges to an User field you create on that content type. Looking at the screenshot provided on the module's page, it looks like it will do everything you ask for, albeit a little bit differently.
http://drupal.org/project/nodeaccess_userreference
Here's a brief scenario.We
Here's a brief overview.
We have a department content type. Departments have sub departments and therefore a sub department content type is in place. A sub department has teams, which means that there is a teams dept. content type. Node reference module helps me connect the three content types ( you guessed it, I'm using D6). Anyhow, there are over 35k users which can browse through any department and view any team page.
But, some team pages should not be accessible to anyone. Only a few users. The list of users is not static, meaning that a manager can add/remove members of a private team anytime.
Here's where using roles becomes the issue. If user A blongs to department A he/she should not be able to view a private team that belongs to department B. Access restrictions via a role would allow any user who has it view any private page.
I hope I explained my situation clear enough.
Thanks
Gotcha. In that case, I'd
Gotcha. In that case, I'd definitely give the Node Access User Reference module a try, especially since you say managers need to be able to add and remove users. If that module ends up not fitting for some reason, I'd try searching the contrib modules for various combinations of "node", "user", and "access".
Nodeaccess_userreference
Nodeaccess_userreference module is installed and seems to do the trick.