New SQL Server User cannot view databases when logging into SSMS

This sounds like the same issue you're running into...

The problem is that for a database that is offline or has been auto-closed, collation comes back as NULL, and SSMS assumes it's because you don't have permission.

The fix is to go to Object Explorer Details, right-click the column header list, uncheck Collation, and refresh the Databases node. You should see all of the databases on the server at this point.

More detail can be found in Microsoft Connect #354291 and Microsoft Connect #354322

SQL Server "users" have two parts to them.

1. The server login. Defined as server level, and maybe associated with server roles (e.g. dbcreator: "Members of the dbcreator fixed server role can create, alter, drop, and restore any database"). Map Windows users to server roles (some of this is done automatically, but depends on the version of SQL Server¹)

2. Database users. These are created by database, given database roles (e.g. "dbo" for full control ("database owner") or "dbreader" to be able to read data). When create these are associated with a server login.

You can define server and database roles to give specific permissions).

See SQL Server Books Online (or on MSDN) for more details.

So you need to, using the administrator account, create a server login for your Windows user account, and give it access to the databases you need to work with. If you are defining things (tables, views, stored procs, ...) you really need "dbo" role, or quite some work for finer grained control.

Remember to test the application with just the access that application needs (e.g. it is a rare application that would create/drop/alter views or tables).

¹ In SQL Server 2005 the host machine's local Administrators group is mapped to a login with "sysadmin" server role, in 2008 you specify which accounts are to be so mapped in the setup).