|
|
Roadmap - Questionaire Responses for AA CAMP 2004 |
Back to
index
(editors)
Back to
index
(techies/administrators)
Add new suggestion
(editors)
Add new suggestion
(techies/administrators)
1. Main problems and annoyances you encounter when using ActionApps
2. Features suggested for future development versions of ActionApps
End user permissions module
There is currently a need for an end user permissions
module. This module would provide the following:
- Authentication for native AA end user systems like
Alerts
- Authentication for end user modules plugged in using
module system
- Ability to use as authentication method for other PHP
apps on the same server
- Ability to use as simple directory level HTTP
authentication for HTML pages that wrap around and
ActionApps site
- Single user profile for each user that is tied into all of
these applications
- Ability to add custom fields to the user profile
- Ability to track information that users have accessed
from AA and Alerts (future)
- Record level authentication (e.g. for reading individual
AA articles) (future)
Some of the work for this is already underway for the
Alerts system. However, new demands that are beyond
what we are doing for Alerts could emerge quickly (see
list above).
Sponosorhship: Depending on cost, these features
could be sponsored by the CEH and PKRN projects
currently managed by Commons Group
3. Comments About Usablility
4. General future development suggestions
Submited by:
Mark Surman
|
 |
APC
ActionApps is a free software content management system initiated by
the Association for Progressive Communications (APC) APC - Internet and ICTs for social justice and development |