You appear to understand this, but just in case... you do not always have to specify the schema, as long as the schema is the user's default schema.
So you can handle this at the login level of SQL Server. A login can be set to default to, say, the schema 'MySchema'. For this login, the table
mySchema.Orders would be the default for that user, addressable as simply
This isn't used often, since it can get confusing, but it is a fully functional way of doing this. But note: if you don't have the table
mySchema.Orders in your database, the system WILL look for
dbo.Orders as well. This is great if you want some tables personalized and some in common - bad if the
mySchema users should not have access to