Schema Design Question

Let me explain what I'm trying to do and see if I can get any suggestions. I have some tables in a database to track "Required Reading" so that users who login must read documents by a certain date.

My first idea was to have a table called Reading that would store each UserID and every DocID from the Documents table. Then when the User logged in I would do a SELECT * FROM Reading WHERE UserID = 'User1' to filter down to all of the documents for the current user. So if I have 10 users and 10 documents then I would have 100 records in the Reading table.

The only problem with that is that every user logged in would have the Reading table open at the same time but no two users should ever be editing the same record. The user would have an exclusive recordset based on his UserID. I just don't know if this would cause a conflict.

Documents
-----------------
DocID nvarchar(16) (PrimaryKey)
Revision nvarchar(8)
RevisionDate smalldatetime
DueDate smalldatetime

Reading
----------------
UserID nvarchar(16) (PrimaryKey)
DocID nvarchar(16) (PrimaryKey)
Read bit
ReadDate smalldatetime

The second idea is to have the same Documents table but when a user logs in, create them a unique table. So if User1 logs in I would check to see if a User1 table exists and if not create it. The same for User2 etc.

User1
------------------
DocID nvarchar(16) (PrimaryKey)
Read bit
ReadDate smalldatetime

User2
------------------
DocID nvarchar(16) (PrimaryKey)
Read bit
ReadDate smalldatetime


Which would be a better schema design?

What would be the best way to index the tables?