Scenario: User is leaving company, and potentially with local replica of important company data on laptop. Business owner wishes to ensure the local replica is destroyed on user’s machine without having to send the IT heavies around and do it manually.
Idea: could an agent be developed and triggered that after a user next replicates (probably not date specific, but at NEXT replication) that will delete either data or design programmatically without the user’s intervention on user’s local replica, hence rendering it useless?
Subject: Delete users local replica of db programmatically
Hi Paul,
I have encountered this need at every firm I have worked at, and many users will tell you that once you provide access to a local replica, consider the access irrevocable. I don’t disagree with this line of thought, but there are things you can do to make things difficult. This is what I do. 1) Set the lowest level of access to the database for users to Reader. I do this by setting the domain to Reader access (*/MY-CO = Reader). 2) Add a role to the database called EVERYONE, but do not include the */MY-CO entry in this group. 3) Use a group to set security to the database, and give that group access to the EVERYONE role (#EVERYONE-GROUP = READER & EVERYONE ROLE). 4) Add a reader field to every document and set it to EVERYONE. Once in place, this is what happens. A) Employee is hired, added to #EVERYONE-GROUP and creates local replica) B) Employeee is terminated, and is removed from #EVERYONE-GROUP but is not yet removed from the Notes domain. C) Employee replicates, and since they still have Reader access to the database, they replicate the change to their group membership and they lose access to the EVERYONE role. D) Employee loses access to the documents in the database. This solution works on 6.x and below, but there is an issue with this solution on 7 for which an SPR is in the works (has to do with how local replicas handle group and role membership changes) but once that bug is resolved, it should work for 7 also. Keep in mind that any shrewd user will, upon sensing their imminent release, immediately export, download, save, and otherwise extract any relevant IP from the db’s they want before they handover or replicate again.