1) Basic Site visitor (all public content only)
2) Tenant Contact (public content, private links & tenant manual)
3) Building management (public content, private links, tenant manual & construction manual)
1) the ability to link users to buildings: Since each building would have different PDF tenant & construction manuals, etc., how might we be able to easily attach tenants (users) to the correct buildings (and thus the correct protected content?), especially if this content is not static, but generated via a property search via our custom plugin and ensure that they cannot access w/o proper (S2Member) login credentials? Could we use a URI fragment such as "Tenant Manual" combined with a GUID or is there a more elegant way?
2) What secure technologies are protect the passworded area?
3) Our 1000+ members are dovetailed into the same membership DB as our site admins, yes (no?) how can we ensure that they cannot accidentally gain access to the WP admin pages (prevent a PHP injection, etc.)
I don't see a problem. However, if you choose to use Custom Capabilities, teaching your client how to add Custom Capabilities on a per-User basis will help. You can click [Edit] next to a User in your list of Users and then add comma-delimited Capabilities in the s2Member Profile section toward the bottom.
I'm fairly sure that this is all possible with S2Member -- I just need to make sure that it will be an easy process for our clients to add users to the correct properties with the correct permissions.
Statistics: Posted by Jason Caldwell — July 11th, 2011, 5:34 pm
Statistics: Posted by Jason Caldwell — July 8th, 2011, 11:19 pm
1) Basic Site visitor (all public content only)
2) Tenant Contact (public content, private links & tenant manual)
3) Building management (public content, private links, tenant manual & construction manual)
1) the ability to link users to buildings: Since each building would have different PDF tenant & construction manuals, etc., how might we be able to easily attach tenants (users) to the correct buildings (and thus the correct protected content?), especially if this content is not static, but generated via a property search via our custom plugin and ensure that they cannot access w/o proper (S2Member) login credentials? Could we use a URI fragment such as "Tenant Manual" combined with a GUID or is there a more elegant way?
2) What secure technologies are protect the passworded area?
3) Our 1000+ members are dovetailed into the same membership DB as our site admins, yes (no?) how can we ensure that they cannot accidentally gain access to the WP admin pages (prevent a PHP injection, etc.)
Statistics: Posted by Cristián Lávaque — July 8th, 2011, 10:04 pm
Statistics: Posted by jagedge26 — July 8th, 2011, 4:26 pm