Re: Help w/Multi User Admins

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 15837
interpreted = N
texte = >I was also wondering if that would exlude them from each other (or would I use protect?) I dont know how musch of a issue this would be in the beginning but obviously I would like to offer each a secure place for there info.That's what I meant about getting fancy later. No, they will not be excluded from each other, because anyone in the Admin group is considered to be Admin everywhere. So you might want to create a Store1, Store2, Store3 group, and change the templates so they use [protect Store1], etc. You should know this does not prevent store owners from 'hacking', in that they can still write WebDNA that stomps over other stores if they really want to. The only 100% protection you have is when you don't allow any store owner to save template files to disk.I'd also institute a Zero Tolerance policy of hacking -- tell your vendors that if you ever discover one store owner hacking another store (or doing other nasty things to the server), then you kick them out without a refund.Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Help w/Multi User Admins (Grant Hulbert 1997)
  2. Re: Help w/Multi User Admins (Grant Hulbert 1997)
  3. Re: Help w/Multi User Admins (list@9way.com 1997)
  4. Help w/Multi User Admins (list@9way.com 1997)
>I was also wondering if that would exlude them from each other (or would I use protect?) I dont know how musch of a issue this would be in the beginning but obviously I would like to offer each a secure place for there info.That's what I meant about getting fancy later. No, they will not be excluded from each other, because anyone in the Admin group is considered to be Admin everywhere. So you might want to create a Store1, Store2, Store3 group, and change the templates so they use [protect Store1], etc. You should know this does not prevent store owners from 'hacking', in that they can still write WebDNA that stomps over other stores if they really want to. The only 100% protection you have is when you don't allow any store owner to save template files to disk.I'd also institute a Zero Tolerance policy of hacking -- tell your vendors that if you ever discover one store owner hacking another store (or doing other nasty things to the server), then you kick them out without a refund.Grant Hulbert, V.P. Engineering | ==== eCommerce for the Rest of Us ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ Grant Hulbert

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

WebMerchant when CC network is down (1998) Emailer port change (1997) Searching multiple fields from one form field (1997) oops private message leaked into talk list (1997) WebCat2 beta 11 - new prefs ... (1997) apparently to problem isolated (1997) Webcatalog on MacOs (2000) WebCat2 - [format thousands] (1997) User Defined Sorting (1997) Help with getting rpm file (2002) Weird Problem (1997) Small problem (2001) THANKS!!! ShipCosts.db and debugging (1997) searchable list archive (1997) [HIDEIF] inside [FOUNDITEM] (1997) PCS Emailer's role ? (1997) AppleScript: Tell application:app location? (1998) Spiders (1998) Some Questions (1997) default value from Lookup (was Grant, please help me) (1997)