Authorisation/en - Revision history

TR at 09:11, 21 January 2026

2026-01-21T09:11:42Z

FuzzyBot: Updating to match new version of source page

2026-01-21T08:48:03Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2021-03-10T18:08:33Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2017-07-06T08:52:17Z

Updating to match new version of source page

FuzzyBot: Updating to match new version of source page

2017-06-12T17:25:30Z

Updating to match new version of source page

TR at 14:53, 21 January 2016

2016-01-21T14:53:05Z

TR at 14:50, 21 January 2016

2016-01-21T14:50:26Z

TR at 14:49, 21 January 2016

2016-01-21T14:49:54Z

Diana Nayis: Created page with "Authorisation"

2015-12-15T15:23:03Z

Created page with "Authorisation"

New page

__FORCETOC__

In this program you can define authorisation groups and the different authorisation levels for access to functions in Marathon

== Authorisation ==

Authorisation in Marathon can be set on functionality level and on user level.

The setup consists of different authorisation groups that can be set with several authorisations per function. The users are then connected to authorisation groups; either a general one or per company.

== Authorisation groups ==

Register authorisation groups in System: Authorisation groups.
It is possible to create a group with only one person, if a certain authorisation concerns only one. You can also set a limit to a group concerning monetary amounts on purchase orders, final approval and/or insertions. For purchase orders, this means that the employee only can save purchase orders up to the stated amount. For final approval, the limit means the highest amount that the employee can approve. It is possible to make a partial approval in case the total amount of the invoice exceeds the limit. Concerning insertions, the employee can only save insertions up to the stated amount.

== Distribution of authorisations ==

The distribution of authorisations is done in System: Authorisation. There are three different authorisation levels; reading rights, writing rights and none. Reading rights is to a certain extent restricted.

Click on the blue symbol on the left of the subsystems in order to expand the list and deepen into functionalities. If authorisation is set on subsystem level, it will be valid for all the functionalities in that subsystem.

{{ExpandImage|ALM-BEH-EN-grafik2.png}}

== Connect employee and authorisation group ==

In System: Base register/General/User, under the tab Authorisation, it is possible to add a user to either a general authorisation group or to authorisation groups per company.

[[Category:ALM-BEH-EN]] [[Category:Manuals]] [[Category:System]]

@@ Line 11: / Line 11: @@
 An amount limit for purchase orders, final approvals, insertions and vouchers can be set for the authorisation group.
-For purchase orders, this means that only PO: s with a maximum of the specified amount can be saved.
+For '''purchase orders''', this means that only PO: s with a maximum of the specified amount can be saved.
-For final approval, the upper limit for what can be approved is specified. It is possible to approve part of the invoice amount if the invoice value exceeds the limit.
+For '''final approval''', the upper limit for what can be approved is specified. It is possible to approve part of the invoice amount if the invoice value exceeds the limit.
-For insertions, only insertions with a maximum of the specified amount can be saved.
+For '''insertions''', only insertions with a maximum of the specified amount can be saved.
-For vouchers, vouchers that exceed the amount cannot be approved.
+For '''vouchers''', vouchers that exceed the amount cannot be approved.
 == Authorisation settings ==

← Older revision		Revision as of 08:48, 21 January 2026
Line 1:		Line 1:
		+	<htmltag tagname="style">p a.image{border:1px rgb(0,0,0) solid;box-sizing:content-box;}</htmltag>
−	__FORCETOC__

		⚫	= Authorisation=
−	In this program you can define authorisation groups and the different authorisation levels for access to functions in Marathon

		⚫	Authorisation groups are set up with authorisations per function. Users are then linked to authorisation groups, either general or per company.
⚫	== Authorisation ==

		⚫	== Authorisation groups==
−	Authorisation in Marathon can be set on functionality level and on user level.
		⚫	Register the authorisation groups in System \| Authorisation, Authorisation group tab.

		+	{{ExpandImage\|ALM-BEH-EN-Bild1.png}}
⚫	~~The setup consists of different authorisation~~ groups ~~that~~ ~~can~~ ~~be set~~ with ~~several~~ authorisations per function. ~~The users~~ are then ~~connected~~ to authorisation groups; either a general ~~one~~ or per company.

		+	An amount limit for purchase orders, final approvals, insertions and vouchers can be set for the authorisation group.
⚫	== Authorisation groups ==
		+	For purchase orders, this means that only PO: s with a maximum of the specified amount can be saved.
		+	For final approval, the upper limit for what can be approved is specified. It is possible to approve part of the invoice amount if the invoice value exceeds the limit.
		+	For insertions, only insertions with a maximum of the specified amount can be saved.
		+	For vouchers, vouchers that exceed the amount cannot be approved.

		+	== Authorisation settings ==
⚫	Register authorisation groups in System: Authorisation ~~groups~~.
		+	Authorisation settings are set in System \| Authorisation, Authorisation tab. Choose between authorisation levels: None, Read and Write. The Read authorisation does not grant any permissions if it is a function that is write-only.
−	It is possible to create a group with only one person, if a certain authorisation concerns only one. You can also set a limit to a group concerning monetary amounts on purchase orders, final approval and/or insertions. For purchase orders, this means that the employee only can save purchase orders up to the stated amount. For final approval, the limit means the highest amount that the employee can approve. It is possible to make a partial approval in case the total amount of the invoice exceeds the limit. Concerning insertions, the employee can only save insertions up to the stated amount.

		+	If the authorisation is set on a subsystem level, the authorisation will be valid for the complete subsystem. Click on the blue plus sign to deepen and specify authorisation for de different functions.
−	== Distribution of authorisations ==

		+	{{ExpandImage\|ALM-BEH-EN-Bild2.png}}
−	The distribution of authorisations is done in System: Authorisation. There are three different authorisation levels; reading rights, writing rights and none. Reading rights is to a certain extent restricted.

		⚫	==Connect user and authorisation group==
−	Click on the blue symbol on the left of the subsystems in order to expand the list and deepen into functionalities. If authorisation is set on subsystem level, it will be valid for all the functionalities in that subsystem.
		⚫	In System \| Base registers \| Users, under the Authorisation tab, you can connect a user to a General authorisation group or authorisation group Per company, if the authorisation shall vary between companies.

−	{{ExpandImage\|ALM-BEH-EN-~~grafik2~~.png}}	+	{{ExpandImage\|ALM-BEH-EN-Bild3.png}}

		+	[[Category:ALM-BEH-EN]]
⚫	== Connect user and authorisation group ==
		+	[[Category:General]]
−
		+	[[Category:Manuals]]
⚫	In System: Base ~~register/General/User~~, under the ~~tab~~ Authorisation, it is ~~possible to add~~ a user to ~~either~~ a ~~general~~ authorisation group or to authorisation ~~groups~~ ~~per~~ company.
−
−	[[Category:ALM-BEH-EN]] [[Category:Manuals]] [[Category:System]] [[Category:System/Authorisation]]

@@ Line 22: / Line 22: @@
 {{ExpandImage|ALM-BEH-EN-grafik2.png}}
-== Connect employee and authorisation group ==
+== Connect user and authorisation group ==
 In System: Base register/General/User, under the tab Authorisation, it is possible to add a user to either a general authorisation group or to authorisation groups per company.

@@ Line 24: / Line 24: @@
 == Connect employee and authorisation group ==
-In Backoffice: Base register/General/User, under the tab Authorisation, it is possible to add a user to either a general authorisation group or to authorisation groups per company.
+In System: Base register/General/User, under the tab Authorisation, it is possible to add a user to either a general authorisation group or to authorisation groups per company.
-[[Category:ALM-BEH-EN]]
+[[Category:ALM-BEH-EN]] [[Category:Manuals]] [[Category:System]] [[Category:System/Authorisation]]

@@ Line 11: / Line 11: @@
 == Authorisation groups ==
-Register authorisation groups in {{pth|System|Authorisation groups}}.
+Register authorisation groups in System: Authorisation groups.
 It is possible to create a group with only one person, if a certain authorisation concerns only one. You can also set a limit to a group concerning  monetary amounts on purchase orders, final approval and/or insertions. For purchase orders, this means that the employee only can save purchase orders up to the stated amount. For final approval, the limit means the highest amount that the employee can approve. It is possible to make a partial approval in case the total amount of the invoice exceeds the limit. Concerning insertions, the employee can only save insertions up to the stated amount.
 == Distribution of authorisations ==
-The distribution of authorisations  is done in {{pth|System< Authorisation}}. There are three different authorisation levels; reading rights, writing rights and none. Reading rights is to a certain extent restricted.
+The distribution of authorisations  is done in System: Authorisation. There are three different authorisation levels; reading rights, writing rights and none. Reading rights is to a certain extent restricted.
 Click on the blue symbol on the left of the subsystems in order to expand the list and deepen into functionalities. If authorisation is set on subsystem level, it will be valid for all the functionalities in that subsystem.
@@ Line 24: / Line 24: @@
 == Connect employee and authorisation group ==
-In {{pth|System|Base register/General/User}}, under the tab Authorisation, it is possible to add a user to either a general authorisation group or to authorisation groups per company.
+In Backoffice: Base register/General/User, under the tab Authorisation, it is possible to add a user to either a general authorisation group or to authorisation groups per company.
-[[Category:ALM-BEH-EN]] [[Category:Manuals]] [[Category:System]]
+[[Category:ALM-BEH-EN]]