Admin Tools enables Alfresco administrators to create and manage users and groups from within Share, set application preferences, manage categories and tags, and browse the system information in the node browser.
The Admin Tools option is visible on the menu bar only if you are an Administrator user or a user who is a member of the ALFRESCO_ADMINISTRATORS group.
You see the list of tools on the left-side of the page. The first set of tools are for general Alfresco administration:
The remaining tools are grouped into the following categories:
Choose one of the available themes:
The new theme applies the CSS and image assets across all pages.
You'll see the Upload File window.
You can choose to upload any image you like but there are some recommendations for suitable sizes for the image. The maximum recommended image height for your image file is 48 pixels.
The file you chose shows in the Upload File window. If it's not the right file, click Remove to select another file.
The newly uploaded file now becomes the logo for Alfresco.
The Category Manager page shows a tree structure of the categories created in the system. The top level is called Category Root and by default, the following sub-categories are listed:
You can categorize files using parent categories and their child categories.
When you hover over the category name, you see the available action icons for:
Edit category (),
Add category (
), and
Delete category (
).
When using Solr, there maybe a delay before the new category appears in a search query until after Solr has been reindexed. Categories are eventually consistent. Categories are available for use across all sites and by all users.
The category is deleted from the system. Any content is removed from that category label.
By default, the search criteria PATH:"/" is shown in the Node Browser field for the workspace://SpacesStore repository store. Each store is an area of the repository. The nodes contained within each store are organized hierarchically. The node displayed is the root node of the selected store.
The default search type is set to fts-alfresco. For most administrative tasks, you can use the default search type. See Alfresco Full Text Search reference [15] for more detail.
The details of the properties, aspects, children, parents, associations, source associations, and permissions are displayed for the node.
The Tag Manager page shows a list of the tags that have been created, the name of the user who created or modified the tag, and the date on which the change was made.
If there are no tags in the system, you see the message: No tags found.
When you hover over the
right hand Actions column, you see the available
action icons for: Edit tag ()
and Delete tag (
).
The tag is deleted from the system and removed from any content where it was previously tagged.
Social content publishing allows you to use content from Alfresco to publish out through other social platforms or delivery mechanisms.
The current out-of-the-box support is for the following social platforms:
Any content asset from the document library can be published to any appropriate publishing channel.
The framework allows you to develop and plug-in additional channels.
https://bitly.com/a/sign_up
The profile settings show your email address and indicate that your email address is not yet verified.
You will receive a verification email for the address you used in the profile settings. Check your inbox and follow the instructions in the email to confirm the address.
You will then see a page showing that the account verification was successful.
This screen shows two fields in the Legacy API Key section: Login and API key.
For example:
You will use the values of these two fields to configure Alfresco.
Add the following properties using the Login and API key values from the Bitly settings page. For example:
urlshortening.bitly.username=anexample urlshortening.bitly.api.key=R_a6689e13748149ccb35c4e1afadbb03e
Where:
On a new installation, there are no existing channels created.
Choose from the following channels:
You see the Facebook Request for permission page stating that Alfresco is requesting permission for access to your Facebook account.
You see a popup window indicating that a new Facebook channel has been created. The Facebook channel displays on the Channel Manager page.
You see the Flickr Sign in to Yahoo authorization page.
You are then requested to authorize the Alfresco can access the Flickr account.
You see a popup window indicating that a new Flickr channel has been created. The Flickr channel displays on the Channel Manager page.
You see the LinkedIn authorization page.
LinkedIn will then list the applications that you have authorized.
The LinkedIn channel displays on the Channel Manager page.
You see the SlideShare authorization page.
SlideShare will then list the applications that you have authorized.
The SlideShare channel displays on the Channel Manager page.
You see the Twitter authorization page requesting the user name and password of the Twitter account.
You see a popup window indicating that a new Twitter channel has been created. The Twitter channel displays on the Channel Manager page.
You see the Alfresco Channel Authentication page requesting your user name and password for the new YouTube channel.
You see a popup window indicating that a new YouTube channel has been created. The YouTube channel displays on the Channel Manager page.
When a channel is created, all users are set to the Consumer role by default. This means that no users will have permission to publish content except the administrative user.
You see the Manage Permissions page for the channel. Permissions are inherited by default. To disable inherited permissions, click Inherit Permissions, and then click Yes.
You see the relevant authorization pages for the channel.
You are asked to confirm that you wish to delete this channel.
The channel is deleted and the channel icon is removed from the Channels Management page.
A replication job specifies the content to be replicated; the day and time the job is to be performed; and the target location for the replicated content.
The job is controlled by the Replication Service, and it calls the Transfer Service, which allows folders and content to be automatically copied between Alfresco repositories. A replication job can be run according to a schedule or on-demand.
By default, any replicated content is read-only in the target repository. This ensures the integrity of the content is not affected by uncontrolled updates.
The Replication Jobs page displays a summary of recently run jobs and a list of existing replication jobs. In this list, use the menu provided to sort the jobs by Status, Name, and Last Run Date.
The job appears highlighted in the list and its details appear on the right side of the page.
The Create New Replication Job page appears. Fields marked with an asterisk (*) are required.
Navigate the repository and click Add to the right of each space that you want to include in the payload. This content will be replicated (copied) from the repository to the transfer agent (target file system) when the job is run. Click OK.
Navigate the Transfer Target Groups and click Select to the right of the target. Click OK.
Select the Schedule job check box, then enter the date and time the job is to run. Specify the repeat period for this job.
The job created appears highlighted in the Jobs list. The job details appear on the right side of the page.
For each job in this list, you can perform any of the following actions to manage and maintain the jobs:
The job appears highlighted in the list and its details appear on the right side of the page.
The Status section on the right side of the page indicates that the job is running. The date and time the job started is displayed.
An icon () to the left of the job name
indicates a job is currently running.
The Status section on the right side of the page indicates the start time of the selected job.
The job is stopped and a report is created.
The job appears highlighted in the list and its details appear on the right side of the page.
The Edit Replication Job page appears.
Add and remove source items as necessary. Click Remove to the right of a single item to remove it. Click Remove All beneath the list to remove all items.
Deselect the Enabled check box to prevent the job from being run.
The main page displays the updated job details.
The job appears highlighted in the list and its details appear on the right side of the page.
A message prompts you to confirm the deletion of the selected job.
The selected job is deleted from the jobs list.
The remote report is the transfer report from the receiving system. This report indicates whether files were created, updated, modified, or deleted as part of the transfer.
The job appears highlighted in the list and its details appear on the right side of the page.
The selected report displays on the details page of the Repository Document Library.
You"ll see the User Search page.
The New User page appears. Fields marked with an asterisk (*) are required.
Field | What is it? |
---|---|
First Name | Type the first name of the new user. |
Type an email address that the user will use for receiving Alfresco notification emails. | |
User Name | Type a user name for the new user. You can use any name but it is |
Password | Type a password for the user account. Note: Enter a minimum of five
characters otherwise you'll not be able to see the Create
User button.
|
Verify Password | Repeat the password. Make sure that you type the same password you typed in the Password field. |
You must enter a minimum of one (1) character. The search is not case sensitive.
The groups appear beneath the Groups list. Click a group to remove it.
This information is not required. When no quota is provided, the user has no space limitations.
Content quotas are disabled by default. You can change the default setting by adding the following property to the alfresco-global.properties file: system.usages.enabled=true.
If you intend to immediately create another user, click Create and Create Another. This creates the user account specified and clears the fields without returning you to the User Search page.
User Name,First Name,Last Name,E-mail Address,,Password,Company,Job Title,Location,Telephone,Mobile, Skype,IM,Google User Name,Address,Address Line 2,Address Line 3,Post Code,Telephone,Fax,Email
You don't need values for all the headings for each users. For example, the following sample shows the content of a CSV file using Microsoft Excel:
Save the file as a .csv file, which you can then upload into Alfresco.
You'll see the User Search page.
The CSV file has an extension of .csv.
The users from the CSV file are uploaded into Alfresco and you see the Upload Results page showing the list of user names and status. An email will be sent to the user informing them of their new Alfresco user account.
You can register any number of users in Alfresco (see Setting up Alfresco authentication and security [47]) and a license is only consumed when the registered user logs in to Alfresco and is authorized.
If a user attempts to login for the first time and the user license limit has been exceeded, the login attempt will fail.
When the user first logs in to Alfresco using their user name and password, the login mechanism validates the login credentials. If the system is within the license limit, the user can successfully login to Alfresco, otherwise the login attempt fails and the user remains in the Never Authorized state. Periodically, the Authorization Audit Service job runs to check usage conforms to the license limit. The period at which the Authorization Audit Service job runs is set to default values in repository.properties as follows:
# Configuration of the Authorization Audit trigger # By default every second day of the week at 03:00 authorization.audit.day=2 authorization.audit.hour=3 authorization.audit.minute=0
These properties can be overridden in alfresco-global.properties.
To authorize an administrative user, follow the steps below:
The leftmost pane shows all the top-level user groups.
The individual user is added as a child to the ALFRESCO_ADMINISTRATORS group.
The User Search page displays a list of all users along with their authorisation status. The authorization state of the user added to the ALFRESCO_ADMINISTRATORS group has changed from Never Authorized to Authorized.
Users from the ALFRESCO_ADMINSTRATORS permissions group cannot be deauthorized without being first removed from this group.
To deuathorize a user, follow the steps below:You see the User Search page.
The result table displays the user name along with its authorization status.
You will be prompted to confirm your action.
The relevant user's authorization status changes to Deauthorized.
You see the User Search page.
The search is not case sensitive.
In the results table, you can click the column headings to sort the results.
In the first column, a green dot indicates the user account is currently enabled; a red dot indicates the account is disabled.
You'll see the User Search page.
The Edit User page appears.
You see the User Search page.
A message prompts you to confirm that you want to delete the user account.
You see the User Search page.
You see the Edit User page.
A check mark indicates the account for the current user will be disabled.
On the User Profile page, the Account Status shows as Disabled. On the User Search page, the user displays in the search results list with a red dot, indicating the account is disabled.
You see the User Search page.
You see the Edit User page.
The password is case sensitive.
You see the User Search page.
You see the Edit User page.
The leftmost pane displays all top-level user groups.
System groups are created in the background, for example, when you create a site. You can show these groups so that you can edit the Display Name, add users, or delete the group.
The content can be subgroups and/or individual users. Text at the bottom of this panel indicates the number of groups and users that belong to the selected group.
The search is not case sensitive.
In the results table, click the column headings to sort the results as desired.
The leftmost pane displays all top-level user groups.
The New Group page appears. Fields marked with an asterisk (*) are required.
Field | What is it? |
---|---|
Identifier | This is a name that the system uses to identify the group. Once you have created the group, you cannot change this identifier. |
Display Name | This is the group name that shows in Alfresco where you manage groups and also is the name shown to members of this group. |
If you intend to immediately create another group at the same level, click Create and Create Another. This creates the group specified and clears the fields without returning you to the Groups page.
The leftmost pane shows all the top-level user groups.
The search is not case sensitive.
The leftmost pane shows all the top-level user groups.
You must enter a minimum of one (1) character. The search is not case sensitive.
A message prompts you to confirm the deletion.
The leftmost pane shows all the top-level user groups.
The individual user or group is added as a child to the group selected in the panel.
Links:
[1] https://docs.alfresco.com/../tasks/admintools-open.html
[2] https://docs.alfresco.com/../concepts/admintools-prefs.html
[3] https://docs.alfresco.com/../tasks/admintools-catmanager.html
[4] https://docs.alfresco.com/../tasks/admintools-nodebrowser.html
[5] https://docs.alfresco.com/../tasks/admintools-tagbrowser.html
[6] https://docs.alfresco.com/../concepts/admintools-channelsman-intro.html
[7] https://docs.alfresco.com/../concepts/admintools-replication-intro.html
[8] https://docs.alfresco.com/../concepts/admintools-users-intro.html
[9] https://docs.alfresco.com/../concepts/admintools-groups-intro.html
[10] https://docs.alfresco.com/../concepts/ch-administering.html
[11] https://docs.alfresco.com/../concepts/admintools.html
[12] https://docs.alfresco.com/../tasks/admintools-theme.html
[13] https://docs.alfresco.com/../tasks/admintools-logo.html
[14] https://docs.alfresco.com/site-content-tag.html
[15] https://docs.alfresco.com/../concepts/rm-searchsyntax-intro.html
[16] https://docs.alfresco.com/../tasks/admintools-channelsman-bitly.html
[17] https://docs.alfresco.com/../tasks/admintools-channelsman.html
[18] https://docs.alfresco.com/../tasks/admintools-channel-permission.html
[19] https://docs.alfresco.com/../tasks/admintools-channel-reauth.html
[20] https://docs.alfresco.com/../tasks/admintools-channel-delete.html
[21] https://docs.alfresco.com/../tasks/admintools-channel-fb.html
[22] https://docs.alfresco.com/../tasks/admintools-channel-flickr.html
[23] https://docs.alfresco.com/../tasks/admintools-channel-lnkin.html
[24] https://docs.alfresco.com/../tasks/admintools-channel-slideshare.html
[25] https://docs.alfresco.com/../tasks/admintools-channel-twtr.html
[26] https://docs.alfresco.com/../tasks/admintools-channel-youtube.html
[27] https://docs.alfresco.com/../concepts/sysadmin-subsystem-props.html
[28] https://docs.alfresco.com/../tasks/admintools-replication-view.html
[29] https://docs.alfresco.com/../tasks/admintools-replication-create.html
[30] https://docs.alfresco.com/../concepts/admintools-replication-manage.html
[31] https://docs.alfresco.com/../tasks/admintools-replication-reports.html
[32] https://docs.alfresco.com/../tasks/admintools-replication-run.html
[33] https://docs.alfresco.com/../tasks/admintools-replication-cancel.html
[34] https://docs.alfresco.com/../tasks/admintools-replication-edit.html
[35] https://docs.alfresco.com/../tasks/admintools-replication-delete.html
[36] https://docs.alfresco.com/admintools-replication-delete.html
[37] https://docs.alfresco.com/admintools-replication-edit.html
[38] https://docs.alfresco.com/../tasks/admintools-user-create.html
[39] https://docs.alfresco.com/../tasks/admintools-upload-users.html
[40] https://docs.alfresco.com/../concepts/license-process.html
[41] https://docs.alfresco.com/../tasks/admintools-user-view.html
[42] https://docs.alfresco.com/../tasks/admintools-user-edit.html
[43] https://docs.alfresco.com/../tasks/admintools-user-delete.html
[44] https://docs.alfresco.com/../tasks/admintools-user-disable.html
[45] https://docs.alfresco.com/../tasks/admintools-user-password.html
[46] https://docs.alfresco.com/../tasks/admintools-user-group-membership.html
[47] https://docs.alfresco.com/auth-intro.html
[48] https://docs.alfresco.com/../tasks/license-authorize.html
[49] https://docs.alfresco.com/../tasks/license-deauthorize.html
[50] https://docs.alfresco.com/admintools-user-create.html%23adminconsole-user-create__four
[51] https://support.alfresco.com/
[52] https://docs.alfresco.com/admintools-user-edit.html
[53] https://docs.alfresco.com/admintools-user-delete.html
[54] https://docs.alfresco.com/admintools-user-view.html
[55] https://docs.alfresco.com/admintools-user-disable.html
[56] https://docs.alfresco.com/../tasks/admintools-group-browse.html
[57] https://docs.alfresco.com/../tasks/admintools-group-search.html
[58] https://docs.alfresco.com/../tasks/admintools-group-new.html
[59] https://docs.alfresco.com/../tasks/admintools-group-edit.html
[60] https://docs.alfresco.com/../tasks/admintools-group-delete.html
[61] https://docs.alfresco.com/../tasks/admintools-group-membership.html
[62] https://docs.alfresco.com/admintools-group-edit.html
[63] https://docs.alfresco.com/admintools-group-delete.html
[64] https://docs.alfresco.com/admintools-group-browse.html