Accessing the Corporate Dashboard
The Corporate Dashboard allows board members of issuers to view the shareholder registry and to initiate corporate actions.
These are the steps for gaining access to the corporate dashboard:
Your organization needs to be a client of Aktionariat. To become a client, get in touch with email@example.com.
Either Aktionariat (for newly created accounts) or an existing corporate administrator invites you by e-mail. They can do so in the section “Administrators” of the “Issuer” tab of the dashboard.
Open the invitation e-mail sent to you from firstname.lastname@example.org (do not forget to check your spam filter and promotions tab) and click the accept button in the e-mail on a device with a large screen. The dashboard is opened in the web browser.
Click the sign-in button on the dashbaord, scan the QR code with the Aktionariat app (install the app first if you didn't do so already), and sign the appearing message in the app.
You are in!
Once the above steps are completed, you can sign in to the Corporate Dashboard by performing the following steps:
- Visit dashboard.aktionariat.com on a computer or tablet with a large screen (not your phone).
- Click the sign-in button. When doing this for the first time, a QR-code appears.
- Open the Aktionariat app, go to the connect tab and scan the QR-code shown on the website.
- The web page will show a “waiting for signature” dialog. Open the Aktionariat app and wait for the signature request to appear.
- Approve the signature request in the app. The website will now automatically navigate to the dashboard if you are authorized. If you are not authorized, an error message will appear below the sign-in button.
Note that signing in will set a session cookie that will keep you signed in until it either expires (after a few days without visiting the Dashboard) or you explicitly sign out.
Note that the dashboard only functions with apps that fully implement the WalletConnect standard, most notably the Aktionariat Portfolio app. Many other wallets (including MetaMask) lack support for the “eth_signTransaction” function, which we require for signing multi-signature transactions.