Basic Security via PDL

[k1sr]

Hi,

I'm trying to add some basic security to a workbook, but which will check if
the user (via Application.UserName) exists in an Exchange PDL, and if it
does, then give them access

This is a template workbook and therefore saved thousands of times as
different file names... I need the PDL check to run live, so I can add more
users by adding them to the PDL, giving new users access to all previously
saved workbooks from the template and the template itself...

it's easy enough to imbed a list of users into the workbook/code, however,
adding a new user this way will only effect new files created from the new
template from that point on - the new user would not be able to access
existing files (not good)...

Before you ask, I cannot use the Rights Management functionality in Office,
as we do not have it installed, and I'm using additional code to render the
workbook useless unless macros are enabled...

Thanks in advance...

 

[Doug Glancy]

k1sr,

As far as the updating of new users goes, you should load the template from
an centrally available addin that can be updated to users' computers. You
could look at Charles Williams Addin Loader for help with that:

http://www.decisionmodels.com/downloads.htm#addload

hth,

Doug

 

[k1sr]

Thanks Doug...

This is all a little above me - not entirely sure how to use it, however, I
figure this will only work for access to the template, rather than files
previously created with the template before the new user was added...

This is my main issue - I need new users to be able access all historical
files created by the template...

Cheers

 

[Doug Glancy]

k1sr,

I think you are right. What I'm thinking of requires an addin on their
computer that identifies some trait that distinguishes each of the workbooks
before, or as, they are opened. Many people use Custom Document
properties, which can be set on the template by right clicking in Windows
Explorer when the workbook is closed. But as you say, that doesn't help
now.

If the template and it's workbooks all contained a unique name then your
addin could check for that as the workbook opens.

At any rate, security that depends on the code in the workbook is flimsy
because they can always open the workbook with macros disabled.

Another approach would be to set the security through Windows. At my
workplace, I'd ask the IT person to create a security group in Active
Directory, to which I could add or delete users, much like your Personal
Distribution List. You, or the IT person, could then limit access to the
folders/files in question to that security group.

Sorry if you've thought of that already, but it's the best I've got.

Doug