Advice for client mailing list db

HCL Domino Domino Forum
1

We’ve got a project to create a client list database that will be used for managing invitations and RSVPs to various bank events.

My initial thought was each client would be a notes document with fields like name, address, email, etc…Then we send clients an invite (email or letter) that directs them to a URL of an RSVP form where they can respond yes or no. The RSVP form would either update the client’s document, or create a new doc (response doc to client doc?) for just that event since there will be multiple events throughout the year. Maybe use an ‘invitation id’ to tie things together?

One big challenge is how to secure it? Clients may need to update their personal info from time to time, so it would be nice if the RSVP form could have an “update address” option for them, but for this we’d need to call up their existing info from the database, and that’s where it gets tricky.

If they come from the web as Anonymous with Author or Editor access, then anyone could potentially get to the views/documents containing sensitive client info. If we do Depositor, then they can’t look at or edit any of their existing stuff, i.e. “we have your current address as: xyz… need to update it?” etc. won’t work

If we don’t use Anonymous, then Domino authentication requires a person doc in our NAB. I’m quite certain my Domino Administrator will not be happy with me requesting to add several thousand new person docs to the address book, nor would I want to setup/maintain that.

Any other ways of authenticating them/securing the database without creating a person doc for each of them?

Comments on how to best structure the database/documents?

All thoughts appreciated, thanks!

-Nico

2

Subject: Create a secondary NAB

You’ll have to create one document per person you want to login.

But you don’t have to put them in the main NAB. You can setup a secondary address book on the server your application will be and create those users in there. You don’t have to use Admin client to create them as they don’t need any certificates (i.e. notes ids) to login through the web. Just add them in the secondary NAB using creation actions in the db.

To be able to login those users, you’ll need to create a directory assistance db. Check Admin help to have more details with the howto.

Renaud

3

Subject: web login

If you want clients to login then yes, you’d need to provide them username and password and manage those users (and pay for them) There’s no way round that

If you’re willing to do this you can of course use a different domain for their details, as long as the two domains are cross-certified they can have access to the client db, or simply use a replica on the public server