Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

As your organization's financial information is sensitive, your Phocas site administrator controls who can access the Financial Statements module and what they can see and do there. This security gives your organization the freedom to share financial dashboards, charts, analysis results and so on, without

...

having to worry about who can see what.

This page gives an overview of options your administrator can set up for you.

Table of Contents
maxLevel2
minLevel2

Permission to customize statements

You may want users to be able to view and analyze financial statements in Phocas without permitting them to change the structure of the statement. This is simple, because by default users don't have permission to customize statements and when they go to the Actions menu they won't see the Statements option in the dropdown (as shown in the screenshots below).

...

Giving someone permission to customize statements is done via a checkbox in the user’s profile setting. Your administrator can do this for you.

Control database access

...

For example, in your organization’s financial statements:

  • If you are a Regional Manager of Australia, you might only see data for Australia (not UK and USA).

  • If you are a Warehouse Manager, you might only see the operating costs for your branch.

  • If you are a member of the Sales team, you might only see the Gross Margin and higher-level information.

In accordance with the examples above, the following factors impact your access to your organization’s financial information:

Database access

Your administrator manages who can access a database and what information they can see within

...

that database. If your organization’s financial data comes from more than one database, they can set restrictions for multiple databases, for individual users or groups. For example,

...

your administrator can set a default restriction on a database, so

...

users

...

can see ‘budget’ but not ‘profit’ information.

If your financial data is coming from more than one database, restricitions can be set for multiple databases.

...

Advanced administrators can also restrict access to sync source data to ensure that no one, even other administrators, can query the financial data.

User restrictions

If, for example,

...

your organization only

...

wants your local branch managers to see the data

...

relating to

...

their branch’s budgets

...

, your administrator can restrict access, so that each manager only sees the information relevant to them

...

.

...

These restrictions can be

...

customized at a very fine level and can be applied to one database at a time

...

, for individual users or groups. For example, a user can have access to

...

the Cost of

...

Sales data in one database

...

but not in another.

Both database and user restrictions can byeset for individual users or groups.

Information for administrators

Manage permission to customize financial statements

Financial Statements permissions

There are two categories of users in Financial Statements:

  • Users who can view and analyze the Financial Statements, and ultimately use the information to make business decisions. This user is sometimes referred to as a ‘consumer’.

  • Users who have permission to manage the financial statements in your organization, which includes customizing existing statements, adding new statements and restricting access to certain accounts within statements. This user is sometimes referred to as a ‘producer’. Your administrator can give you this permission via the Manage Custom Statement setting.

If you have permission to manage and customize the financial statements, you will see the Customize Statements option in the Statements menu.

Image Added

Financial Statements account restrictions

As mentioned above, users with the Manage Custom Statements permission can restrict access to accounts. This means that within the Financial Statements module, users might be able to view high-level totals of certain accounts, such salaries or commissions but not the low-level transactional detail. This restriction protects sensitive information.